<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss1full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:cc="http://web.resource.org/cc/" xmlns="http://purl.org/rss/1.0/">

<channel rdf:about="http://www.schneier.com/blog/">
<title>Schneier on Security</title>
<link>http://www.schneier.com/blog/</link>
<description>A blog covering security and security technology.</description>
<dc:creator />
<dc:date>2009-11-20T13:21:14-06:00</dc:date>
<dc:rights>Copyright 2009 Bruce Schneier</dc:rights>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.3-en" />


<items>
<rdf:Seq>
<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2009/11/interview_with_15.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2009/11/failblog_on_sec.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2009/11/denial-of-servi.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2009/11/a_taxonomy_of_s.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2009/11/stabbing_people.html" />
</rdf:Seq>
</items>

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/schneier/fulltext" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /></channel>


<item rdf:about="http://www.schneier.com/blog/archives/2009/11/interview_with_15.html">
<title>Interview with Me</title>
<link>http://www.schneier.com/blog/archives/2009/11/interview_with_15.html</link>
<description>&lt;p&gt;&lt;a href="http://risky.biz/RB2-schneier"&gt;Yet another&lt;/a&gt; interview with me.  This one is audio, and was conducted in Rotterdam in October.&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=X9pKv2CASuw:-FZtY0hB_V4:2mJPEYqXBVI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=2mJPEYqXBVI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=X9pKv2CASuw:-FZtY0hB_V4:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=X9pKv2CASuw:-FZtY0hB_V4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2009-11-20T13:21:14-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2009/11/failblog_on_sec.html">
<title>FailBlog on Security</title>
<link>http://www.schneier.com/blog/archives/2009/11/failblog_on_sec.html</link>
<description>&lt;p&gt;Funny: &lt;a href="http://failblog.org/2009/11/07/career-fair-fail/"&gt;career fair fail&lt;/a&gt;.&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=hxzcrQTXU-Q:2AHrw_4JnU0:2mJPEYqXBVI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=2mJPEYqXBVI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=hxzcrQTXU-Q:2AHrw_4JnU0:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=hxzcrQTXU-Q:2AHrw_4JnU0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2009-11-20T11:11:19-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2009/11/denial-of-servi.html">
<title>Denial-of-Service Attack Against CALEA</title>
<link>http://www.schneier.com/blog/archives/2009/11/denial-of-servi.html</link>
<description>&lt;p&gt;&lt;a href="http://www.wired.com/threatlevel/2009/11/calea/"&gt;Interesting&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;The researchers say they've found a vulnerability in U.S. law enforcement wiretaps, if only theoretical, that would allow a surveillance target to thwart the authorities by launching what amounts to a denial-of-service (DoS) attack against the connection between the phone company switches and law enforcement.

&lt;p&gt;[...]&lt;/p&gt;

&lt;p&gt;The University of Pennsylvania researchers found the flaw after &lt;a href="http://www.computerworld.com/s/article/9140717/How_to_DDOS_a_federal_wiretap?taxonomyId=17"&gt;examining the telecommunication industry standard&lt;/a&gt; ANSI Standard J-STD-025, which addresses the transmission of wiretapped data from telecom switches to authorities, according to IDG News Service. Under the 1994 Communications Assistance for Law Enforcement Act, or Calea, telecoms are required to design their network architecture to make it easy for authorities to tap calls transmitted over digitally switched phone networks.&lt;/p&gt;

&lt;p&gt;But the researchers, who &lt;a href="http://www.wired.com/images_blogs/threatlevel/2009/11/calea.pdf"&gt;describe their findings in a paper&lt;/a&gt;, found that the standard allows for very little bandwidth for the transmission of data about phone calls, which can be overwhelmed in a DoS attack. When a wiretap is enabled, the phone company's switch establishes a 64-Kbps Call Data Channel to send data about the call to law enforcement. That paltry channel can be flooded if a target of the wiretap sends dozens of simultaneous SMS messages or makes numerous VOIP phone calls "without significant degradation of service to the targets' actual traffic."&lt;/p&gt;

&lt;p&gt;As a result, the researchers say, law enforcement could lose records of whom a target called and when. The attack could also prevent the content of calls from being accurately monitored or recorded.&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;The &lt;a href="http://www.wired.com/images_blogs/threatlevel/2009/11/calea.pdf"&gt;paper&lt;/a&gt;. &lt;a href="http://www.crypto.com/blog/calea_weaknesses/"&gt;Comments&lt;/a&gt; by Matt Blaze, one of the paper's authors.&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=vFJ2N9wa6mw:A448qk0Su6Q:2mJPEYqXBVI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=2mJPEYqXBVI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=vFJ2N9wa6mw:A448qk0Su6Q:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=vFJ2N9wa6mw:A448qk0Su6Q:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2009-11-20T06:11:17-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2009/11/a_taxonomy_of_s.html">
<title>A Taxonomy of Social Networking Data</title>
<link>http://www.schneier.com/blog/archives/2009/11/a_taxonomy_of_s.html</link>
<description>&lt;p&gt;At the Internet Governance Forum in Sharm El Sheikh this week, there was a conversation on social networking data.  Someone made the point that there are several different types of data, and it would be useful to separate them.  This is my taxonomy of social networking data.&lt;/p&gt;

&lt;ol&gt;&lt;li&gt;&lt;b&gt;Service data&lt;/b&gt;.  Service data is the data you need to give to a social networking site in order to use it.  It might include your legal name, your age, and your credit card number.

&lt;p&gt;&lt;li&gt;&lt;b&gt;Disclosed data&lt;/b&gt;.  This is what you post on your own pages: blog entries, photographs, messages, comments, and so on.&lt;/p&gt;

&lt;p&gt;&lt;li&gt;&lt;b&gt;Entrusted data&lt;/b&gt;.  This is what you post on other people's pages.  It's basically the same stuff as disclosed data, but the difference is that you don't have control over the data -- someone else does.&lt;/p&gt;

&lt;p&gt;&lt;li&gt;&lt;b&gt;Incidental data&lt;/b&gt;.  Incidental data is data the other people post about you.  Again, it's basically same same stuff as disclosed data, but the difference is that 1) you don't have control over it, and 2) you didn't create it in the first place.&lt;/p&gt;

&lt;p&gt;&lt;li&gt;&lt;b&gt;Behavioral data&lt;/b&gt;.  This is data that the site collects about your habits by recording what you do and who you do it with.&lt;/ol&gt;&lt;/p&gt;

&lt;p&gt;Different social networking sites give users different rights for each data type.  Some are always private, some can be made private, and some are always public.  Some can be edited or deleted -- I know one site that allows entrusted data to be edited or deleted within a 24-hour period -- and some cannot. Some can be viewed and some cannot.&lt;/p&gt;

&lt;p&gt;And people &lt;i&gt;should&lt;/i&gt; have different rights with respect to each data type.  It's clear that people should be allowed to change and delete their disclosed data.  It's less clear what rights they have for their entrusted data.  And far less clear for their incidental data.  If you post pictures of a party with me in them, can I demand you remove those pictures -- or at least blur out my face?  And what about behavioral data?  It's often a critical part of a social networking site's business model.  We often don't mind if they use it to target advertisements, but are probably less sanguine about them selling it to third parties. &lt;/p&gt;

&lt;p&gt;As we continue our conversations about what sorts of fundamental rights people have with respect to their data, this taxonomy will be useful.&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=gvvj9WK9rhg:6Xhi4o0E9c4:2mJPEYqXBVI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=2mJPEYqXBVI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=gvvj9WK9rhg:6Xhi4o0E9c4:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=gvvj9WK9rhg:6Xhi4o0E9c4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2009-11-19T12:51:17-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2009/11/stabbing_people.html">
<title>Stabbing People with Stuff You Can Get Through Airport Security</title>
<link>http://www.schneier.com/blog/archives/2009/11/stabbing_people.html</link>
<description>&lt;p&gt;"&lt;a href="http://www.ncbi.nlm.nih.gov/pubmed/17325460?itool=EntrezSystem2.PEntrez.Pubmed.Pubmed_ResultsPanel.Pubmed_RVDocSum&amp;ordinalpos=257"&gt;Use of a pig model to demonstrate vulnerability of major neck vessels to inflicted trauma from common household items&lt;/a&gt;," from the &lt;i&gt;American Journal of Forensic Medical Pathology&lt;/i&gt;.&lt;/p&gt;

&lt;blockquote&gt;&lt;b&gt;Abstract&lt;/b&gt;.  Commonly available items including a ball point pen, a plastic knife, a broken wine bottle, and a broken wine glass were used to inflict stab and incised wounds to the necks of 3 previously euthanized Large White pigs. With relative ease, these items could be inserted into the necks of the pigs next to the jugular veins and carotid arteries. Despite precautions against the carrying of metal objects such as knives and nail files on board domestic and international flights, objects are still available within aircraft cabins that could be used to inflict serious and potentially life-threatening injuries. If airport and aircraft security measures are to be consistently applied, then consideration should be given to removing items such as glass bottles and glass drinking vessels. However, given the results of a relatively uncomplicated modification of a plastic knife, it may not be possible to remove all dangerous objects from aircraft. Security systems may therefore need to focus on measures such as increased surveillance of passenger behavior, rather than on attempting to eliminate every object that may serve as a potential weapon.&lt;/blockquote&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=95QpXApHNI4:QNaggqEEjRg:2mJPEYqXBVI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=2mJPEYqXBVI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=95QpXApHNI4:QNaggqEEjRg:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/schneier/fulltext?a=95QpXApHNI4:QNaggqEEjRg:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/schneier/fulltext?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2009-11-19T07:10:41-06:00</dc:date>
</item>


</rdf:RDF>
