<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://purl.org/rss/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

  <channel rdf:about="http://lwn.net/headlines/267109/">
    <title>LWN: Comments on "LCA: Bruce Schneier on the two sides of security"</title>
    <link>http://lwn.net/Articles/267109/</link>
    <description>
This is a special feed containing comments posted
to the individual LWN article titled &quot;LCA: Bruce Schneier on the two sides of security&quot;.

    </description>

    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>2</syn:updateFrequency>
    <items>
      <rdf:Seq>
	<rdf:li resource="http://lwn.net/Articles/269061/rss" />
	<rdf:li resource="http://lwn.net/Articles/268191/rss" />
	<rdf:li resource="http://lwn.net/Articles/267706/rss" />
	<rdf:li resource="http://lwn.net/Articles/267699/rss" />
	<rdf:li resource="http://lwn.net/Articles/267678/rss" />
	<rdf:li resource="http://lwn.net/Articles/267670/rss" />
	<rdf:li resource="http://lwn.net/Articles/267666/rss" />
	<rdf:li resource="http://lwn.net/Articles/267652/rss" />
	<rdf:li resource="http://lwn.net/Articles/267618/rss" />
	<rdf:li resource="http://lwn.net/Articles/267595/rss" />
	<rdf:li resource="http://lwn.net/Articles/267586/rss" />
	<rdf:li resource="http://lwn.net/Articles/267551/rss" />
	<rdf:li resource="http://lwn.net/Articles/267506/rss" />
	<rdf:li resource="http://lwn.net/Articles/267487/rss" />
	<rdf:li resource="http://lwn.net/Articles/267297/rss" />
	<rdf:li resource="http://lwn.net/Articles/267286/rss" />
	<rdf:li resource="http://lwn.net/Articles/267277/rss" />
      
      </rdf:Seq>
    </items>

  </channel>
    <item rdf:about="http://lwn.net/Articles/269061/rss">
      <title>LCA: Bruce Schneier on the two sides of security</title>
      <link>http://lwn.net/Articles/269061/rss</link>
      <dc:date>2008-02-13T13:39:09+00:00</dc:date>
      <dc:creator>ekj</dc:creator>
      <description>
      SELinux is a bad example.&lt;p&gt;

I, like most sysadmins I know have been turning it off. But not for any reason of irrational fear like you suggest, but rather precisely for the reason one should do it, according to the Schneier you quote: &lt;b&gt;For many people it just plain isn't worth it.&lt;/b&gt;&lt;p&gt;

I assume I'm some uncertain amount safer when I have it turned on, hard to say precisely how much, but it'll certainly have some positive effect, prevent some types of attack from succeeding.&lt;p&gt;

But I -KNOW- from personal first hand experience that:

&lt;ul&gt;
&lt;li&gt;It is complex. Complexity is -bad- for security.
&lt;li&gt;I don't understand it. Not even after having spent probably a week spesifically trying to understand it. Possibly, I'm just stupid, but that's the way it is.
&lt;li&gt;It takes a lot of time to configure it correctly for any non-trivial setting.
&lt;li&gt;Having it turned on causes a lot of headaches with stuff that otherwise &quot;just works&quot;.
&lt;/ul&gt;

Put differently: The COST of running with SELinux is known and HIGH. The benefit is unknown, but assumed moderately positive. Not enough positive to defend turning it on though.&lt;p&gt;

Being more secure does not help if the added work is MORE than the gain in security. I don't use SELinux for the same reason I wouldn't support banning all airplanes; both would probably improve security, but the cost is to high.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/268191/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/268191/rss</link>
      <dc:date>2008-02-07T17:09:58+00:00</dc:date>
      <dc:creator>dkite</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
I wouldn't like to fly with a pilot that doesn't fear what he does. In 
other words, a mistake can kill. The fact that this fear is real and 
vivid and acted upon makes air travel as safe as it is.

People act foolishly when afraid because they don't know what to do. On 
the other hand people regularly are hurt or killed at their workplace 
because they didn't know that they should be afraid.

How many times has people in this readership been afraid to apply a 
change to a working system? The fear moves you to double check, get other 
input, set up a test system, whatever.

Personally, when I fear things that I encounter regularly, I find out 
what to do. Not to allay fear, but to know how to act safely.

Derek (who in his work is regularly in situations that could kill him)
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267706/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267706/rss</link>
      <dc:date>2008-02-04T00:40:50+00:00</dc:date>
      <dc:creator>ikm</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
All fears are very rational in the end, so if your palms still sweat after the 100th time, try
another approach at understanding what you're actually afraid of :)
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267699/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267699/rss</link>
      <dc:date>2008-02-03T22:25:32+00:00</dc:date>
      <dc:creator>man_ls</dc:creator>
      <description>
      You point at a good strategy to make our irrational fears go away, or at least keep them under control: not knowing how something works can make us fearful. Therefore, learning how things work can take us a long way to controlling our fears. And that is exactly what engineers have been doing since before History started: learning how things work and then controlling them. That is how people learned to build boats and entered the sea; how they built huge temples which defied our sense of stability; and even how they built those megaliths which still amaze us.
&lt;p&gt;
The point is, even if you know the Bernoulli effect by heart, even if you understand the principles of aeronautics and have compiled flight crash statistics yourself, you may not be able to stop your palms from sweating the first time your plane lifts in the air. Or even the hundredth time. Still, it's not that bad for a grassland monkey! :D
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267678/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267678/rss</link>
      <dc:date>2008-02-03T18:16:50+00:00</dc:date>
      <dc:creator>ikm</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt; I'm not sure I follow you here. If a pack of wolves suddenly appears behind me, how is the
fear I feel a result of being dependent? I'm dependent on what exactly, on the wolves? On me?
On some other people appearing and saving me? If I just hear wolves howling and the hairs on
the back of my head suddenly all stand up, where is the dependency? Or when I find a snake in
the grass and my palms get all sweaty? When lightning strikes beside my tree? I'm just trying
to understand your statement, honestly.&lt;/font&gt;

You feel fear because you can't do much about the situation. You're dependent on something
else which would resolve the situation. You have to hope that the wolves aren't after you,
that you're not stumping on a snake, or that the lightning isn't striking at you. You're
dependent on the whimsical mercies of a chance. You're dependent just because you don't seem
to be able to resolve the situation yourself.

&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt; But e.g. with elevators we are not talking about a high risk or a low risk; statistics tell
us that casualties due to cabin falls are zero, or so close to zero that they are not
meaningful.&lt;/font&gt;

Who cares about what they say? I've met many people who were saying many different things. Why
would I want to believe? Let me have my own statistics and draw my own conclusions. What I
know is that falling from great heights is dangerous and can be lethal, that metals are very
tough, that the elevator's engines are very powerful and can easily tear me apart -- that's
what I KNOW. Don't you think it kinda contradicts what these statistics of yours say? Why
would I want to believe them then?! You can say that nuclear power plants are safe, and I
would never agree -- just because they inherently contain sources of dangers, no matter how
perfectly confined they are. Same with elevators.

While I personally don't have any elevators' fears, I assert that the line of thought I
presented is totally legitimate and has its merits, and I also think this is the way any
living being makes its assessments.

&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt; In contrast, with cars we all know that regardless of the condition of driver and car we are
dependent on the good will of all other drivers. Even if everything else is in perfect
condition, if a drunk driver invades your lane or doesn't stop at a red light you are done.&lt;/font&gt;

I would disagree here. A good driver is not just someone who knows how to turn left and right
and how to tell red from green, but a person who actually knows his stuff, sees problems
coming, sees if other persons don't behave right on the road, anticipates everything and
doesn't get into problems as a result.

What you push here is that we should trust somebody who is presumably much more clever than
us. What I push is that, first of all, we should trust ourselves, and if somebody wants to
earn our trust, he should indeed earn it first. I personally see no problems in how people do
their assessments -- they might not always be right, but they are doing the right thing. If
they are wrong, it's probably lack of information -- but you can't just shove this information
down their throats and expect them to accept it. Most probably, it will be rejected as being
too different from what they know already -- and that's the right thing for them to do.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267670/rss">
      <title>Lemons vs silver bullets ?</title>
      <link>http://lwn.net/Articles/267670/rss</link>
      <dc:date>2008-02-03T13:50:53+00:00</dc:date>
      <dc:creator>anchorsystems</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
There is a good blog post at Financial Cryptography that goes into
more detail than Bruce regarding the &quot;lemons&quot; market in security:

&lt;a href=&quot;https://financialcryptography.com/mt/archives/000896.html&quot;&gt;https://financialcryptography.com/mt/archives/000896.html&lt;/a&gt;
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267666/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267666/rss</link>
      <dc:date>2008-02-03T12:37:34+00:00</dc:date>
      <dc:creator>man_ls</dc:creator>
      <description>
      &lt;blockquote type=&quot;cite&quot;&gt;
If we're talking about fear here, we're always talking about dependency, because fear is
always a result of being dependent.
&lt;/blockquote&gt;
I'm not sure I follow you here. If a pack of wolves suddenly appears behind me, how is the fear I feel a result of being dependent? I'm dependent on what exactly, on the wolves? On me? On some other people appearing and saving me? If I just hear wolves howling and the hairs on the back of my head suddenly all stand up, where is the dependency? Or when I find a snake in the grass and my palms get all sweaty? When lightning strikes beside my tree? I'm just trying to understand your statement, honestly.
&lt;p&gt;
Precisely for this kind of fears we are very well equipped. For the rest, not so much. You argue that a bunch of statistical numbers are not meaningful, and for some perils you are right: a careful assessment is better than a generic one. But e.g. with elevators we are not talking about a high risk or a low risk; statistics tell us that casualties due to cabin falls are &lt;i&gt;zero&lt;/i&gt;, or so close to zero that they are not meaningful. &lt;a href=&quot;http://www.cdc.gov/eLCOSH/docs/d0300/d000397/d000397.html&quot;&gt;6 passenger deaths per year in the US&lt;/a&gt;, mostly due to falls into an open shaft and entanglement of clothes into the door. We don't depend on the internals or the people who maintain them; we shouldn't even worry about cabin falls. In short: they are safe devices, in the same league as escalators. When the cabin bumps in its way there should be no reason to be fearful, and yet we cannot avoid our hearts racing.
&lt;p&gt;
In contrast, with cars we all know that regardless of the condition of driver and car we are dependent on the good will of all other drivers. Even if everything else is in perfect condition, if a drunk driver invades your lane or doesn't stop at a red light you are done. Here statistics and anecdotal evidence tell us that we are in peril every minute we pass in a car. How come we feel cozy and secure in our vehicles? Once more, bad judgment.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267652/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267652/rss</link>
      <dc:date>2008-02-03T02:58:18+00:00</dc:date>
      <dc:creator>ikm</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
If we're talking about fear here, we're always talking about dependency, because fear is
always a result of being dependent. If we're talking about inabilities to perform assessments
correctly, they are probably because of the ignorance, pure lack of information, or
disinformation, which can also be a result of being dependent (on someone who does all the
assessments instead of you), or on some other conditions.

I would note that anyway, I think our physical ways of evaluating danger are still much better
than just a bunch of worldwide statistical crap, because instead of believing in some generic
and unconditional statistical facts, we can take many things into account which are special
for each situation. E.g, the fact that the driver is sober or drunk makes much difference,
don't you think? So maybe instead of thinking about the annual death rate, you should see how
good the driver is, what kind of shape the car's in, and so on? The fear of elevators can
indeed exist just because of the inability to assess its state (what's there under the hood
anyway? do you know how this crap works? is it really safe? have you ever seen the internals?
many questions. here we're totally dependent on a good will of the people who maintain this
elevator, hence we have fears).
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267618/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267618/rss</link>
      <dc:date>2008-02-02T12:19:11+00:00</dc:date>
      <dc:creator>man_ls</dc:creator>
      <description>
      Not sure what you mean, but this has nothing to do with being dependent. What is really news is that we are so bad at evaluating danger. Schneier has posted innumerable examples, let me give you one more: many people are afraid of elevators, and certainly every time an elevator hits a small bump we all shudder. However, the rational risk is close to null: how many people do you know have died in an elevator? The annual death toll is ludicrous.
&lt;p&gt;
If we were completely rational we would shudder every time we got into a car -- a lot of people die every day in one of those. Our physical ways of evaluating danger are fit for a bunch of monkeys wandering in a savannah, but so outdated for today's world that they are funny. (In fact there is a whole sector of the economy based on this fact: amusement parks, where you feel fear for fun.) 
&lt;p&gt;
You can thus imagine how well suited people are to evaluate computer dangers: very badly. Extensive training and experience is required just to perform rational assessments.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267595/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267595/rss</link>
      <dc:date>2008-02-02T04:48:11+00:00</dc:date>
      <dc:creator>ikm</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
People are just dependent on other people -- is this news, really?
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267586/rss">
      <title>Mitigation strategy</title>
      <link>http://lwn.net/Articles/267586/rss</link>
      <dc:date>2008-02-02T00:45:18+00:00</dc:date>
      <dc:creator>man_ls</dc:creator>
      <description>
      That will protect you from paying attention to what Schneier calls &lt;a href=&quot;http://www.schneier.com/blog/archives/2006/06/movieplot_threa_1.html&quot;&gt;movie-plot threats&lt;/a&gt; (to an extent, as long as you don't go to the movies). But what I gather from his speech is that we are wired to be like this; unfortunately you cannot change this fact with any strategy.
&lt;p&gt;
Maybe watching less TV you can mitigate how &quot;exploitable&quot; this built-in fearful inner self is. TV tends to take advantage of our innermost fears, so maybe frequent watchers are sensitized to security theater. But I tend to think that we actually are wired the way Schneier says: people in other ages (even before there was TV, kids) were as fearful and exploitable as we are now.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267551/rss">
      <title>LCA: Bruce Schneier on the two sides of security</title>
      <link>http://lwn.net/Articles/267551/rss</link>
      <dc:date>2008-02-01T21:33:58+00:00</dc:date>
      <dc:creator>jamesh</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
If you are going to delay disclosure of vulnerabilities, then you need to make sure you aren't
leaking information about those vulnerabilities before that date.

If the project uses CVS or Subversion, then there is no reason that the bad guys wouldn't be
watching the commits.  The contents of the commits may be enough for such a person to deduce
the vulnerability and be able to exploit it in the window the developers have provided (in
addition to the time it takes for people to patch their systems).

So you really want to delay exposure of the commits to the same point where you expose the
vulnerabilities.  With a public CVS/Subversion server, that probably means not committing the
work until that point which is not particularly helpful if you have multiple vulnerabilities
to track.

If you really do want to batch up the security vulnerabilities, perhaps one of the distributed
VCS systems would be appropriate.  The ability to perform disconnected development also means
that it is possible to keep a line of development private but disclose it at a later date with
full history, which is what is wanted here.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267506/rss">
      <title>SELinux: Tradeoff and &quot;felt&quot; vs. &quot;real&quot; security</title>
      <link>http://lwn.net/Articles/267506/rss</link>
      <dc:date>2008-02-01T16:27:58+00:00</dc:date>
      <dc:creator>thias</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Hi Jonathan,

there are at least two different angles regarding SELinux in the context of Bruce LCA keynote:
The nature of security being a tradeoff and the difference between &quot;felt&quot; and &quot;real&quot; security.

If you consider security as a tradeoff, then the fact that SELinux is rather infrequently
deployed is at least a hint toward SELinux being a bad tradeoff: Most people (and I mean
professional sysadmins) tend to think, that the added complexity of SELinux is likely not the
cause of more security - quite the converse.  If you (as a sysadmin) do not understand how
things work an why, you will make bad decisions, and that will make your &quot;real&quot; security
worse.

That does not mean that SELinux is &quot;not secure&quot; - if you are in need of a bulletproof vest,
then please use it!  You have to learn all the necessary stuff about SELinux and you have to
deploy it in a thought out manner, and it will increase your security (considerably!).  But
for most security needs, the tradeoff is bad.

You state that &quot;a system running SELinux may, in fact, be highly secure&quot;.  I would like to
stress the &quot;may&quot;: You just need a small error in your ACLs (which is easily done and not so
easy to detected) or in one of the many SELinux knobs to play with, and your security turns
from &quot;real&quot; to purely &quot;felt&quot;.  And while &quot;felt&quot; security is relevant as Bruce points out,
&quot;felt&quot; without &quot;real&quot; is a real problem :)


regards, thias

PS: I'm a &quot;first day&quot; subscriber and a quite happy one!  Since the topics of Bruce keynote
touch my professional habitat, I just felt the need to comment for the first time :)  Please
keep up the good work at LWN.

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267487/rss">
      <title>LCA: Bruce Schneier on the two sides of security</title>
      <link>http://lwn.net/Articles/267487/rss</link>
      <dc:date>2008-02-01T12:24:47+00:00</dc:date>
      <dc:creator>kleptog</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
The thought occurred to me that perhaps this is one of the things MS did get right. By having
their Patch &amp;lt;day of the week&amp;gt; they provide the feeling that it's all planned, everything is
under control. I wonder what would have happened if the Wireshark guys had annouced they were
doing a proactive audit and that a new release would happen every first day of the month with
all the issues found in the last month.

Now, the free software community to too large to coordinate anything like that. But imagine if
a distributor decided that all non-critical security updates would happen only on wednesdays,
would people &quot;feel&quot; safer due to it being planned, even though you're sacrificing a little
security (a few days delay).
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267297/rss">
      <title>LCA: Bruce Schneier on the two sides of security</title>
      <link>http://lwn.net/Articles/267297/rss</link>
      <dc:date>2008-01-31T14:04:21+00:00</dc:date>
      <dc:creator>ikm</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
My solution to the problem: watch less TV.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267286/rss">
      <title>Excellent stuff!</title>
      <link>http://lwn.net/Articles/267286/rss</link>
      <dc:date>2008-01-31T11:48:59+00:00</dc:date>
      <dc:creator>nix</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Wireshark uses privilege separation now, so problems in the packet dissectors will only
compromise the low-privilege account used to do the packet dissection. :)
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/267277/rss">
      <title>Excellent stuff!</title>
      <link>http://lwn.net/Articles/267277/rss</link>
      <dc:date>2008-01-31T11:40:11+00:00</dc:date>
      <dc:creator>pr1268</dc:creator>
      <description>
      &lt;p&gt;Thank you, Jon, for this article.  This article (and the ten-year timeline part 4, above) certainly contribute to me being a satisfied subscription customer. :-)&lt;/p&gt;

&lt;p&gt;My own thoughts, comments, and epiphanies below:&lt;/p&gt;

&lt;ul&gt;
&lt;li style=&quot;padding-bottom: 10px;&quot;&gt;I openly admit to having been loath to run Wireshark due to its well-publicized patch rate.  I was unaware that this is actually the result of proactive security (instead of &lt;i&gt;reactive&lt;/i&gt;).  Assuming this is the case, the Wireshark developers should serve as a model for all application developers working on security-sensitive software.&lt;/li&gt;

&lt;li style=&quot;padding-bottom: 10px;&quot;&gt;My own experiences with SELinux (way back in the FC2 days) was that controlling SELinux on a system was akin to running a nuclear power plant from the control room.  So many &amp;quot;dials&amp;quot;, &amp;quot;knobs&amp;quot; and &amp;quot;switches&amp;quot; to control, and accidentally throwing one wrong switch could scram the whole system.&lt;/li&gt;

&lt;li style=&quot;padding-bottom: 10px;&quot;&gt;The Transportation Security Agency is the most egregious example of a purely reactionary, horribly-implemented sorry excuse of an ineffective government bureaucracy I've ever seen.  Ironically, I'm not sure that the American public even gets any &lt;i&gt;feeling&lt;/i&gt; of security with the TSA.  I personally don't perceive that I'm any safer (in &lt;i&gt;reality&lt;/i&gt;) due to the TSA.  But, oh well, taxpayers are willing to fund the &lt;i&gt;feeling&lt;/i&gt; of security, and even I can't blame others for these feelings after witnessing the events of 9/11.&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;Just my $0.02 and change...&lt;/p&gt;
      
      </description>
    </item>
</rdf:RDF>

