<?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>2012-02-03T16:18:41-06:00</dc:date>
<dc:rights>Copyright 2012 Bruce Schneier</dc:rights>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.37" />


<items>
<rdf:Seq>
<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/02/friday_squid_bl_312.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/02/the_problems_of_1.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/02/verisign_hacked.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/02/prisons_in_the.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/02/the_idaho_looph.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/01/possibly_the_mo.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/01/biases_in_foren.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/01/liars_and_outli_3.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/01/british_tourist.html" />

<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2012/01/the_nature_of_c.html" />
</rdf:Seq>
</items>

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rdf+xml" href="http://feeds.feedburner.com/schneier/fulltext" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="schneier/fulltext" /><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/2012/02/friday_squid_bl_312.html">
<title>Friday Squid Blogging: Clothing that Keeps an Exercise Journal</title>
<link>http://www.schneier.com/blog/archives/2012/02/friday_squid_bl_312.html</link>
<description><![CDATA[<p>It's called <a href="http://www.engadget.com/2012/02/02/squid-is-a-shirt-that-keeps-an-exercise-journal/">Squid</a>.</p>

<p>As usual, you can also use this squid post to talk about the security stories in the news that I haven't covered.</p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-02-03T16:18:41-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/02/the_problems_of_1.html">
<title>The Problems of Too Much Information Sharing</title>
<link>http://www.schneier.com/blog/archives/2012/02/the_problems_of_1.html</link>
<description><![CDATA[<p><a href="http://i.imgur.com/rsQ93.png">Funny</a>.  Fake, but funny. </p>

<p>Edited to add (2/3): The <a href="http://www.reddit.com/r/funny/comments/owx3v/so_my_little_cousin_posted_on_fb_that_he_was/">rest of the story</a>.</p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-02-03T14:49:54-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/02/verisign_hacked.html">
<title>VeriSign Hacked, Successfully and Repeatedly, in 2010</title>
<link>http://www.schneier.com/blog/archives/2012/02/verisign_hacked.html</link>
<description><![CDATA[<p>Reuters discovered the <a href="http://www.reuters.com/article/2012/02/02/us-hacking-verisign-idUSTRE8110Z820120202">information</a>:</p>

<blockquote>The VeriSign attacks were revealed in a quarterly U.S. Securities and Exchange Commission filing in October that followed new guidelines on reporting security breaches to investors. It was the most striking disclosure to emerge in a review by Reuters of more than 2,000 documents mentioning breach risks since the SEC guidance was published.</blockquote>

<p>The company, unsurprisingly, is saying nothing.</p>

<blockquote>VeriSign declined multiple interview requests, and senior employees said privately that they had not been given any more details than were in the filing. One said it was impossible to tell if the breach was the result of a concerted effort by a national power, though that was a possibility. "It's an ugly, slim sliver of facts. It's not enough," he said.</blockquote>

<p>The problem for all of us, naturally, is if the certificate system was hacked, allowing the bad guys to forge certificates.  (This has, of course, <a href="http://www.schneier.com/blog/archives/2011/09/forged_google_c.html">happened</a> <a href="http://en.wikipedia.org/wiki/DigiNotar#Issuance_of_fraudulent_certificates">before</a>.)</p>

<p>Are we finally ready to accept that the certificate system is completely broken?</p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-02-03T10:49:08-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/02/prisons_in_the.html">
<title>Prisons in the U.S.</title>
<link>http://www.schneier.com/blog/archives/2012/02/prisons_in_the.html</link>
<description><![CDATA[<p>Really good <a href="http://www.newyorker.com/arts/critics/atlarge/2012/01/30/120130crat_atlarge_gopnik?currentPage=all">article</a> on the huge incarceration rate in the U.S., its causes, its effects, and its value:</p>

<blockquote>Over all, there are now more people under "correctional supervision" in America -- more than six million -- than were in the Gulag Archipelago under Stalin at its height. That city of the confined and the controlled, Lockuptown, is now the second largest in the United States.

<p>The accelerating rate of incarceration over the past few decades is just as startling as the number of people jailed: in 1980, there were about two hundred and twenty people incarcerated for every hundred thousand Americans; by 2010, the number had more than tripled, to seven hundred and thirty-one. No other country even approaches that. In the past two decades, the money that states spend on prisons has risen at six times the rate of spending on higher education.</p>

<p>[...]</p>

<p>The trouble with the Bill of Rights, he argues, is that it emphasizes process and procedure rather than principles. The Declaration of the Rights of Man says, Be just! The Bill of Rights says, Be fair! Instead of announcing general principles­ -- no one should be accused of something that wasn't a crime when he did it; cruel punishments are always wrong; the goal of justice is, above all, that justice be done­ -- it talks procedurally. You can't search someone without a reason; you can't accuse him without allowing him to see the evidence; and so on. This emphasis, Stuntz thinks, has led to the current mess, where accused criminals get laboriously articulated protection against procedural errors and no protection at all against outrageous and obvious violations of simple justice. You can get off if the cops looked in the wrong car with the wrong warrant when they found your joint, but you have no recourse if owning the joint gets you locked up for life. You may be spared the death penalty if you can show a problem with your appointed defender, but it is much harder if there is merely enormous accumulated evidence that you weren't guilty in the first place and the jury got it wrong. Even clauses that Americans are taught to revere are, Stuntz maintains, unworthy of reverence: the ban on "cruel and unusual punishment" was designed to <i>protect</i> cruel punishments -- flogging and branding -- that were not at that time unusual.</blockquote></p>

<p>The author mentions the rise of for-profit businesses increasingly running prisons in the U.S., but I don't think he makes the point strongly enough.  There is now a corporate interest in the U.S. lobbying for such things as mandatory minimum sentencing.  </p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-02-02T09:04:12-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/02/the_idaho_looph.html">
<title>The Idaho Loophole</title>
<link>http://www.schneier.com/blog/archives/2012/02/the_idaho_looph.html</link>
<description><![CDATA[<p>Brian C. Kalt (2005), "<a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=691642">The Perfect Crime</a>," Georgetown Law Journal, Vol. 93, No. 2.</p>

<p><b><blockquote>Abstract:</b>  This article argues that there is a 50-square-mile swath of  Idaho in which one can commit felonies with impunity. This is because of the intersection of a poorly drafted statute with a clear but neglected constitutional provision: the Sixth Amendment's Vicinage Clause. Although lesser criminal charges and civil liability still loom, the remaining possibility of criminals going free over a needless technical failure by Congress is difficult to stomach. No criminal defendant has ever broached the subject, let alone faced the numerous (though unconvincing) counterarguments. This shows that vicinage is not taken seriously by lawyers or judges. Still, Congress should close the Idaho loophole, not pretend it does not exist.</blockquote></p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-02-01T06:05:59-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/01/possibly_the_mo.html">
<title>Possibly the Most Incompetent TSA Story Yet</title>
<link>http://www.schneier.com/blog/archives/2012/01/possibly_the_mo.html</link>
<description><![CDATA[<p>The <a href="http://www.cnn.com/2012/01/30/us/new-york-bomb-scare/index.html">storyline</a>:</p>

<ol><li>TSA screener finds two pipes in passenger's bags.

<p><li>Screener determines that they're not a threat.</p>

<p><li>Screener confiscates them anyway, because of their "material and appearance."</p>

<p><li>Because they're not actually a threat, screener leaves them at the checkpoint.</p>

<p><li>Everyone forgets about them.</p>

<p><li>Six hours later, the next shift of TSA screeners notices the pipes and -- not being able to explain how they got there and, presumably, because of their "material and appearance" -- calls the police bomb squad to remove the pipes.</p>

<p><li>TSA does not evacuate the airport, or even close the checkpoint, because -- well, we don't know why.</ol></p>

<p>I don't even know where to begin.</p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-01-31T17:03:31-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/01/biases_in_foren.html">
<title>Biases in Forensic Science</title>
<link>http://www.schneier.com/blog/archives/2012/01/biases_in_foren.html</link>
<description><![CDATA[<p>Some errors in forensic science may be the result of the <a href="http://www.economist.com/node/21543121">biases</a> of the examiners:</p>

<blockquote>Though they cannot prove it, Dr Dror and Dr Hampikian suspect the difference in contextual information given to the examiners was the cause of the different results. The original pair may have subliminally interpreted ambiguous information in a way helpful to the prosecution, even though they did not consciously realise what they were doing.

<p>[...]</p>

<p>This one example does not prove the existence of a systematic problem. But it does point to a sloppy approach to science. According to Norah Rudin, a forensic-DNA consultant in Mountain View, California, forensic scientists are beginning to accept that cognitive bias exists, but there is still a lot of resistance to the idea, because examiners take the criticism personally and feel they are being accused of doing bad science. According to Dr Rudin, the attitude that cognitive bias can somehow be willed away, by education, training or good intentions, is still pervasive. </blockquote></p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-01-31T11:13:27-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/01/liars_and_outli_3.html">
<title><![CDATA[<i>Liars and Outliers</i> Update]]></title>
<link>http://www.schneier.com/blog/archives/2012/01/liars_and_outli_3.html</link>
<description><![CDATA[<p>According to my publisher, <a href="http://www.schneier.com/book-lo.html">the book</a> was printed last week and the warehouse is shipping orders to booksellers today.  Amazon is likely to start shipping books on Thursday.  (Yes, Amazon's <a href="http://www.amazon.com/gp/product/1118143302/ref=as_li_tf_tl?ie=UTF8&tag=counterpane&linkCode=as2&camp=1789&creative=9325&creativeASIN=1118143302">webpage</a> claims that the book will be published on February 21, 2012, but they'll ship copies as soon as they get them -- this ain't Harry Potter.)  The Kindle edition is already shipping.</p>

<p>Those of you who <a href="http://www.schneier.com/book-lo.html#signed">ordered signed copies from me</a> are likely going to have to wait a couple more weeks.  My copies will arrive from the publisher eventually; then I will sign them and ship them on to you.</p>

<p>Reviews are starting to <a href="http://www.forbes.com/sites/adamthierer/2012/01/23/why-doesnt-society-just-fall-apart/">come</a> <a href="http://365.rsaconference.com/blogs/securityreading/2012/01/23/liars-and-outliers-enabling-the-trust-that-society-needs-to-thrive">out</a>. I expect more in the coming month.</p>

<p>At the end of February, I'll be at the <a href="http://www.rsaconference.com/events/2012/usa/index.htm">RSA Conference</a> in San Francisco.  In addition to my other speaking events, <a href="http://www.flyingpenguin.com/">Davi Ottenheimer</a> will interview me about the book at something called <a href="https://365.rsaconference.com/blogs/rsa-conference-blog/2011/12/14/new-for-rsa-conference-2012--the-author-s-studio">The Author's Studio</a>.  I'll be doing two one-hour book signings at the conference bookstore.  And, and this is the best news of all, HP has bought 1,000 copies of the book and will be giving them away at their booth.  I'll be doing a couple of signings there as well.</p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-01-30T13:59:42-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/01/british_tourist.html">
<title>British Tourists Arrested in the U.S. for Tweeting</title>
<link>http://www.schneier.com/blog/archives/2012/01/british_tourist.html</link>
<description><![CDATA[<p>Does <a href="http://www.dailymail.co.uk/news/article-2093796/British-tourists-arrested-America-terror-charges-Twitter-jokes.html">this story</a> make sense to anyone?</p>

<blockquote>The Department of Homeland Security flagged him as a potential threat when he posted an excited tweet to his pals about his forthcoming trip to Hollywood which read: 'Free this week, for quick gossip/prep before I go and destroy America'.

<p>After making their way through passport control at Los Angeles International Airport (LAX) last Monday afternoon the pair were detained by armed guards.</p>

<p>Despite telling officials the term 'destroy' was British slang for 'party', they were held on suspicion of planning to 'commit crimes' and had their passports confiscated.</blockquote></p>

<p>There just as to be more than this story.  The DHS isn't monitoring the Tweets of random British tourists -- they just can't be.</p>

<p>EDITED TO ADD (1/30):  According to DHS documents <a href="http://epic.org/foia/epic-v-dhs-media-monitoring/default.html">received by EPIC</a>, the DHS monitors the Internet, including social media.</p>

<blockquote>In February 2011, the Department of Homeland Security announced that the agency planned to implement a program that would monitor media content, including social media data. The proposed initiatives would gather information from "online forums, blogs, public websites, and messages boards" and disseminate information to "federal, state, local, and foreign government and private sector partners." The program would be executed, in part, by individuals who established fictitious usernames and passwords to create covert social media profiles to spy on other users. The agency stated it would store personal information for up to five years.

<p>[...]</p>

<p>The records reveal that the DHS is paying General Dynamics to monitor the news. The agency instructed the company to monitor for "[media] reports that reflect adversely on the U.S. Government, DHS, or prevent, protect, respond government activities."</p>

<p>[...]</p>

<p>The DHS instructed the company to "Monitor public social communications on the Internet." The records list the websites that will be monitored, including the comments sections of [The New York Times, The Los Angeles Times, the Huffington Post, the Drudge Report, Wired, and ABC News.]"</blockquote></p>

<p>Still, I have trouble believing that this is what happened.  For this to work General Dynamics would have had to monitor Twitter for key words.  ("Destroy America" is certainly a good key word to search for.)  Then, they would have to find out the real name associated with the Twitter account -- unlike Facebook or Google+, Twitter doesn't have real name information -- so the TSA could cross-index that name with the airline's passenger manifests.  Then the TSA has to get all this information into the INS computers, so that the border control agent knows to detain him.  Sure, it sounds straightforward, but getting all those computers to talk to each other that fast isn't easy.  There has to be more going on here.</p>

<p>EDITED TO ADD (1/30):  One reader points out that this story is from the <i>Daily Mail</i>, and that it's prudent to wait for some more reputable news source to report the story.</p>

<p>EDITED TO ADD (1/30):  There's another <a href="http://www.theregister.co.uk/2012/01/30/tweet_deportation/">story</a> from The Register, but they're just using the <i>Daily Mail</i>.</p>

<p>EDITED TO ADD (1/30):  The FBI is <a href="http://www.newscientist.com/blogs/onepercent/2012/01/fbi-releases-plans-to-monitor.html">looking for someone</a> to build them a system that can monitor social networks.</p>

<blockquote>The information comes from a <a href="https://www.fbo.gov/index?s=opportunity&mode=form&id=c65777356334dab8685984fa74bfd636&tab=core&_cview=1">document</a> released on 19 January looking for companies who might want to build a monitoring system for the FBI. It spells out what the bureau wants from such a system and invites potential contractors to reply by 10 February.

<p>The bureau's wish list calls for the system to be able to automatically search "publicly available" material from Facebook, Twitter and other social media sites for keywords relating to terrorism, surveillance operations, online crime and other FBI missions. Agents would be alerted if the searches produce evidence of "breaking events, incidents, and emerging threats."</p>

<p>Agents will have the option of displaying the tweets and other material captured by the system on a map, to which they can add layers of other data, including the locations of US embassies and military installations, details of previous terrorist attacks and the output from local traffic cameras.</blockquote></p>

<p>EDITED TO ADD (1/30):  New reports are <a href="http://www.forbes.com/sites/kashmirhill/2012/01/30/u-k-tourists-deported-due-to-tweet-about-destroying-america/">saying</a> that customs was tipped off about the two people, and their detention was not a result of data mining:</p>

<blockquote>"Based on information provided by the LAX Port Authority Infoline -- a suspicious activity tipline -- CBP conducted a secondary interview of two subjects presenting for entry into the United States," says the spokesperson, who notes that the CBP "denies entry to thousands of individuals" each year. "Information gathered during this interview revealed that both individuals were inadmissible to the United States and were returned to their country of residence."</blockquote>

<p>This makes a lot more sense to me.</p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-01-30T10:52:01-06:00</dc:date>
</item>

<item rdf:about="http://www.schneier.com/blog/archives/2012/01/the_nature_of_c.html">
<title>The Nature of Cyberwar</title>
<link>http://www.schneier.com/blog/archives/2012/01/the_nature_of_c.html</link>
<description><![CDATA[<p><a href="http://www.internetevolution.com/author.asp?doc_id=237983">This</a> was pretty good, I thought:</p>

<blockquote>However, it may be difficult to write military doctrine for many aspects of cyberconflict that are truly revolutionary. Here are no fewer than 10 to consider: 

<ol><li>The Internet is an artificial environment that can be shaped in part according to national security requirements.

<p><li>The blinding proliferation of technology and hacker tools makes it impossible to be familiar with all of them.</p>

<p><li>The proximity of adversaries is determined by connectivity and bandwidth, not terrestrial geography.</p>

<p><li>Software updates and network reconfigurations change cyberbattle space unpredictably and without warning.</p>

<p><li>Contrary to our historical understanding of war, cyberconflict favors the attacker.</p>

<p><li>Cyberattacks are flexible enough to be effective for propaganda, espionage, and the destruction of critical infrastructure.</p>

<p><li>The difficulty of obtaining reliable cyberattack attribution lessens the credibility of deterrence, prosecution, and retaliation.</p>

<p><li>The "quiet" nature of cyberconflict means a significant battle could take place with only the direct participants knowing about it.</p>

<p><li>The dearth of expertise and evidence can make victory, defeat, and battle damage a highly subjective undertaking.</p>

<p><li>There are few moral inhibitions to cyberattacks, because they relate primarily to the use and abuse of data and computer code. So far, there is little perceived human suffering.</ol></blockquote></p>]]></description>
<dc:subject />
<dc:creator>schneier</dc:creator>
<dc:date>2012-01-30T06:02:49-06:00</dc:date>
</item>


</rdf:RDF>

