<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><rss xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:admin="http://webns.net/mvcb/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
    <title>c0t0d0s0.org - Security</title>
    <link>http://www.c0t0d0s0.org/</link>
    <description>the sun in a lighthungry universe</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.3 - http://www.s9y.org/</generator>
    
    

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/C0t0d0s0org-Security" type="application/rss+xml" /><item>
    <title>Yet another security theater</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/320633752/4553-Yet-another-security-theater.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4553-Yet-another-security-theater.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4553</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4553</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    <a onclick="javascript: pageTracker._trackPageview('/extlink/www.schneier.com/blog/archives/2008/06/fever_screening.html');"  href="http://www.schneier.com/blog/archives/2008/06/fever_screening.html">Bruce Schneier</a> linked to <a onclick="javascript: pageTracker._trackPageview('/extlink/www.cdc.gov/eid/content/14/8/pdfs/08-0059.pdf');"  href="http://www.cdc.gov/eid/content/14/8/pdfs/08-0059.pdf">an interesting essay</a> about mass screening of people with infrared thermometry guns. With this devices you can measure the temperature of a person from a certain disctance. But the essay questions the sense of such a method as they compared the results of this IR guns with :<blockquote>We assessed the accuracy of cutaneous infrared thermometry, which measures temperature on the forehead, for detecting patients with fever in patients admitted to an emergency department. Although negative predictive value was excellent (0.99), positive predictive value was low (0.10). Therefore, we question mass detection of febrile patients by using this method.</blockquote>Negative predictive value means "The device says you have no fever and you have really no fever". Negative predictive value stands for "The device says you have fever, and you have really fever." So the system is good at detecting a person without fever, but not at dividing people with a higher (but normal for them) skin temperature and people with fever. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/320633752" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 26 Jun 2008 17:13:48 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4553-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4553-Yet-another-security-theater.html</feedburner:origLink></item>
<item>
    <title>Critical internet infrastructure hacked</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440938/4518-Critical-internet-infrastructure-hacked.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4518-Critical-internet-infrastructure-hacked.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4518</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4518</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    <a onclick="javascript: pageTracker._trackPageview('/extlink/www.securityfocus.com/archive/1/493387');"  href="http://www.securityfocus.com/archive/1/493387">Craig Wright</a> was able to hack into a leading brand of a really critical part of the internet: A Jura F90 with the Jura Internet Connection Kit. And the effects are really devastating. It can force the the admins into a denial-of-service mode:<blockquote>1. Change the preset coffee settings (make weak or strong coffee)<br />
2. Change the amount of water per cup (say 300ml for a short black) and make a puddle</blockquote>In case you didn´t got it already: The <a onclick="javascript: pageTracker._trackPageview('/extlink/www.de.jura.com/home_x/products_home_use/f_line/impressa_f90.htm');"  href="http://www.de.jura.com/home_x/products_home_use/f_line/impressa_f90.htm">F90</a> a coffee machine .... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440938" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 18 Jun 2008 13:41:29 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4518-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4518-Critical-internet-infrastructure-hacked.html</feedburner:origLink></item>
<item>
    <title>Debian openssl problem</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440939/4442-Debian-openssl-problem.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4442-Debian-openssl-problem.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4442</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4442</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    I´ve suspected in a coffee kitchen discussion with a customer after a presentation a few days ago, that the Debian openssl vulnerability will haunt us for a while and hit us from behind while showing us many problemswith our existing internet security infrastructure. I assume i was correct. Fefe explains some of the uprising problems <a onclick="javascript: pageTracker._trackPageview('/extlink/blog.fefe.de/?ts=b6c9ec7e');"  href="http://blog.fefe.de/?ts=b6c9ec7e">in his blog</a>.<br />
 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440939" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 24 May 2008 13:56:51 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4442-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4442-Debian-openssl-problem.html</feedburner:origLink></item>
<item>
    <title>Magnetic dust</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440940/4400-Magnetic-dust.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4400-Magnetic-dust.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4400</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4400</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    A hard disk goes down in flames through the atmosphere and specialists were still able to recover 90 percent of the data: <a onclick="javascript: pageTracker._trackPageview('/extlink/blocksandfiles.com/article/5056');"  href="http://blocksandfiles.com/article/5056">Data recovered from Seagate drive in Columbia shuttle disaster</a>. At the end, data seems to be more resistant then most of us believe, when you put a vast amount of effort behind the recovery.<br />
<br />
This leads me to annother thoughtgame: Let´s assume, you shredder a disk to pieces as tiny as 1 square millimeter. This would just look like dust to you. A modern harddisk stores 200 gigabit per square inch. One square inch are 645.16 square milimeters. Thus a harddisk would store 310 megabits on a square milimeter. Let´s assume 10 bits per byte (for error correction and similar things) and you have 31 megabytes worth of data on one of these pieces of dust. <br />
<br />
It´s just a question of effort to recover the data, when you can yield 10 million euros out of the data (trade secrets, credit card data) it would give you a nice profit when you spend for example 9 million to recover the data.  Yet another reason for cryptography everywhere or you may end up  with degaussing, shreddering and remelt your old harddisks just to be safe. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440940" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 12 May 2008 09:57:00 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4400-guid.html</guid>
    <category>cryptography</category>
<category>security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4400-Magnetic-dust.html</feedburner:origLink></item>
<item>
    <title>Less known Solaris features: About crashes and cores - Part 1: Introduction</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440941/4386-Less-known-Solaris-features-About-crashes-and-cores-Part-1-Introduction.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4386-Less-known-Solaris-features-About-crashes-and-cores-Part-1-Introduction.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4386</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4386</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    No software is without errors. This is a basic law of computer science.  And when there is no bug in the software (by a strange kind of luck) your hardware has bugs. And when there are no bugs in the hardware, cosmic rays are flipping bits. Thus an operating  system needs some mechanisms to stop a process or the complete kernel at once without allowing the system to write anything back to disk and thus manifesting the corrupted state. This tutorial will cover the most important concepts surrounding the last life signs of a system or an application. <br /><a href="http://www.c0t0d0s0.org/archives/4386-Less-known-Solaris-features-About-crashes-and-cores-Part-1-Introduction.html#extended">Continue reading "Less known Solaris features: About crashes and cores - Part 1: Introduction"</a>
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440941" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 09 May 2008 12:45:34 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4386-guid.html</guid>
    <category>core</category>
<category>crash</category>
<category>lksf</category>
<category>security</category>
<category>solaris</category>
<category>sun</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4386-Less-known-Solaris-features-About-crashes-and-cores-Part-1-Introduction.html</feedburner:origLink></item>
<item>
    <title>Unlocking Windows Screensaver via Firewire</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440942/4184-Unlocking-Windows-Screensaver-via-Firewire.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4184-Unlocking-Windows-Screensaver-via-Firewire.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4184</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4184</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Your colleague is at lunch, he or she didn´t loged out, and the screen is locked? And you need the workstation right now? No problem! <a onclick="javascript: pageTracker._trackPageview('/extlink/storm.net.nz/projects/16');"  href="http://storm.net.nz/projects/16">Adam Boileau has a neat solution </a> or this problem. Simply use <a onclick="javascript: pageTracker._trackPageview('/extlink/storm.net.nz/static/files/winlockpwn');"  href="http://storm.net.nz/static/files/winlockpwn">winlockpwn</a> to unlock the system. You colleagues notebook has no Firewire port? No problem, you only have to put a Cardbus Firewire card into the system. Wait for auto installation (Windows autoinstall drivers while screenlocked) and use winlockpwn to get access to the system. <br />
<br />
Don´t hassle around with this strategy to cool down chips and put them in a different system for <a onclick="javascript: pageTracker._trackPageview('/extlink/citp.princeton.edu/memory/');"  href="http://citp.princeton.edu/memory/">the cold boot attack</a>, you can read the memory of the live system.<br />
<br />
How does this hack work? Well, just read this presentation:<a onclick="javascript: pageTracker._trackPageview('/extlink/storm.net.nz/static/files/ab_firewire_rux2k6-final.pdf');"  href="http://storm.net.nz/static/files/ab_firewire_rux2k6-final.pdf">Hit by a Bus: Physical Access Attacks with Firewire </a>. This trick was presented 2 years ago, but you can still use it.  This hack uses a feature of Firewire: It uses DMA for the fast transfer of data. With this capability you can read and write the memory of the system ... and that´s the master key to the kingdom. And to add insult to injury: You can´t really change it, as the DMA is the "Fire in Firewire" as Adam coined it ..<br />
<br />
PS: Where is my credit card ... i need a firewire card for my old notebook <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/wink.png" alt=";-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440942" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sun, 09 Mar 2008 21:04:25 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4184-guid.html</guid>
    <category>firewire</category>
<category>security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4184-Unlocking-Windows-Screensaver-via-Firewire.html</feedburner:origLink></item>
<item>
    <title>Bruce Schneier about security and privacy</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440943/4043-Bruce-Schneier-about-security-and-privacy.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4043-Bruce-Schneier-about-security-and-privacy.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4043</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4043</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Excellent article about the post 9/11 security society - <a onclick="javascript: pageTracker._trackPageview('/extlink/www.wired.com/politics/security/commentary/securitymatters/2008/01/securitymatters_0124');"  href="http://www.wired.com/politics/security/commentary/securitymatters/2008/01/securitymatters_0124">What Our Top Spy Doesn't Get: Security and Privacy Aren't Opposites</a>:<blockquote>But it's still a false dichotomy. There is no security without privacy. And liberty requires both security and privacy.</blockquote> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440943" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 28 Jan 2008 19:26:09 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4043-guid.html</guid>
    <category>security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4043-Bruce-Schneier-about-security-and-privacy.html</feedburner:origLink></item>
<item>
    <title>Aktion "Himmel" - einen Monat später</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440944/4031-Aktion-Himmel-einen-Monat-spaeter.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/4031-Aktion-Himmel-einen-Monat-spaeter.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=4031</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=4031</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Vor etwa einem Monat habe ich ja schon über die Aktion "Himmel" berichtet. Damaligerzeit wurden <a href="http://www.c0t0d0s0.org/permalink/Himmel.html">12.000 Personen</a> verdächtigt, sich Kinderpornographie verschafft zu haben. Die Presse feierte damals die Aktion. <br />
<br />
Worüber man allerdings sehr wenig hoert ist der weitere Verlauf. Ich spekulierte ja seinerzeit, das von dieser Zahl 12000 sehr viel weniger uebrig bleiben wurde. Wie wenig das werden würde, habe ich allerdings auch nicht geahnt ... .  <a onclick="javascript: pageTracker._trackPageview('/extlink/www.koeln.de/artikel/Koeln/Kinderporno-Verdacht-Verfahren-gegen-500-Koelner-eingestellt-39912-1.html');"  href="http://www.koeln.de/artikel/Koeln/Kinderporno-Verdacht-Verfahren-gegen-500-Koelner-eingestellt-39912-1.html">In Köln wurden beispielsweise sämtliche Ermittlungverfahren (500 an der Zahl) eingestellt</a>, da den  Nutzern nichts nachgewiesen werden konnte, was strafrechtlich relevant gewesen wäre. Ich moechte nicht wissen, wieviele Existenzen <a onclick="javascript: pageTracker._trackPageview('/extlink/www.lawblog.de/index.php/archives/2007/12/25/vom-himmel-in-die-holle/');"  href="http://www.lawblog.de/index.php/archives/2007/12/25/vom-himmel-in-die-holle/">ähnlich wie in diesem Fall kaputt gemacht worden sind.</a> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440944" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 24 Jan 2008 18:33:00 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/4031-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/4031-Aktion-Himmel-einen-Monat-spaeter.html</feedburner:origLink></item>
<item>
    <title>WiFi epidemiology</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440945/3957-WiFi-epidemiology.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3957-WiFi-epidemiology.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3957</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3957</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    The paper <a onclick="javascript: pageTracker._trackPageview('/extlink/arxiv.org/PS_cache/arxiv/pdf/0706/0706.3146v1.pdf');"  href="http://arxiv.org/PS_cache/arxiv/pdf/0706/0706.3146v1.pdf">"WiFi Epidemiology: Can Your Neighbors Router Make Yours Sick?"</a> evaluates an interesting thought game: How would a worm that infects WLAN routers spread in a large population of this devices. As a large amount of router devices inherit their architecture from only a few reference design, such an attack may not as remote as you think at the first time. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440945" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 07 Jan 2008 11:31:13 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3957-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3957-WiFi-epidemiology.html</feedburner:origLink></item>
<item>
    <title>Hacking Traffic Message Channel</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440946/3939-Hacking-Traffic-Message-Channel.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3939-Hacking-Traffic-Message-Channel.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3939</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3939</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    One of the nice thing of modern on-board navigation is the availability of traffic information via FM radio (it´s encoded in the RDS). Joern of <a onclick="javascript: pageTracker._trackPageview('/extlink/www.ende-der-vernunft.org/2007/12/30/links-for-2007-12-30/');"  href="http://www.ende-der-vernunft.org/2007/12/30/links-for-2007-12-30/">Ende-der-Vernunft</a> linked to a interesting presentation held on a security conference: <a onclick="javascript: pageTracker._trackPageview('/extlink/dev.inversepath.com/rds/cansecwest_2007.pdf');"  href="http://dev.inversepath.com/rds/cansecwest_2007.pdf">Unusual Car Navigation Tricks: Injecting RDS-TMC Traffic Information Signals</a>. <br />
<br />
It would be interesting to know, if TMCpro is vulnerable as well. TMCpro is a paying-subscriber service (you pay the subscription with you TMCpro enabled receiver). To close the user group it´s nescessary to encrypt the TMC. This may close the vulnerability of the public TMC, as long the the receiver don´t switch to the public service in case the pro signal isn´t available. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440946" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 02 Jan 2008 12:57:51 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3939-guid.html</guid>
    <category>navigation</category>
<category>security</category>
<category>tmc</category>
<category>tmcpro</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3939-Hacking-Traffic-Message-Channel.html</feedburner:origLink></item>
<item>
    <title>"Himmel"</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440947/3911-Himmel.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3911-Himmel.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3911</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3911</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    In den deutschen Postillen wird ja momentan die Polizei für die Aktion "Himmel" gelobt. Beispielsweise <a onclick="javascript: pageTracker._trackPageview('/extlink/www.spiegel.de/panorama/justiz/0,1518,525248,00.html');"  href="http://www.spiegel.de/panorama/justiz/0,1518,525248,00.html">in diesem Artikel im Spiegel</a>. Man denkt nun als erstes: Geschieht diesen Idioten recht. <br />
<br />
Nur wie üblich, hat die Realität ein paar Facetten mehr und wahrscheinlich wird am Ende von der genannten Zahl 12.000 wesentlich weniger uebrig bleiben. Einen interessanten Einblick in die Aktion bietet der Artikel von Udo Vetter, seines Zeichens bloggender Rechtsanwalt im Artikel "<a onclick="javascript: pageTracker._trackPageview('/extlink/www.lawblog.de/index.php/archives/2007/12/25/vom-himmel-in-die-holle/');"  href="http://www.lawblog.de/index.php/archives/2007/12/25/vom-himmel-in-die-holle/">Vom Himmel in die Hölle</a>". Sein Bericht über einen Mandaten zeichnet ein etwas anderes Bild: So wie es aussieht, war auf dem gleichen Server ein Portal für sogenannte Teen-Photos. Teen bedeutet im Sprachgebrauch dieser Branche die Zeitspanne von 18-19. Man mag jetzt davon halten, was man will, aber diese Photos sind legal. Man hat sich jetzt anscheinend nicht allenortens die Mühe gemacht, zu unterscheiden, ob auf das legale oder illegale Portal zugegriffen worden ist.  Mancherorts scheint das blosse Vorhandensein der IP-Addresse in den Logfiles einen hinreichenden Anfangsverdacht ergeben zu haben, ohne das geprüft worden ist, was dieser User wirklich auf dem System gemacht hat.<br />
<br />
Am Ende kam es, dann wie es kommen muss:<blockquote>Mein Mandant, stellte der Staatsanwalt im Abschlussvermerk fest, habe offenbar eine Vorliebe für junge Frauen und lade gezielt solche Bilder aus dem Internet. Einige zehntausend solcher Fotos fand die Polizei auf der Festplatte meines Auftraggebers. Das reichlich bemühte Fazit der Auswerter, wenigstens ein halbes Dutzend der knapp 50.000 Bilder könnte vor Gericht als kinderpornografisch durchgehen, teilte der Staatsanwalt nicht. Es handele sich um legale Inhalte. Für Moral seien die Ermittlungsbehörden nicht zuständig. Der Staatsanwalt stellte das Verfahren ein.</blockquote>Für den Mandanten von Herrn Vetter hatte diese Aktion übrigens doch erhebliche Folgen:<blockquote>Bei meinem Mandanten wurden Büro und Wohnung durchsucht. Seine Frau und sein Chef zogen schon zu Beginn der Aktion die naheliegenden Konsequenzen. Dass mein Mandant nach Monaten einen schmucklosen Einstellungsbescheid ohne ein Wort des Bedauerns erhielt, interessierte sie nicht sonderlich. Über das Umgangsrecht mit den Kindern wird demnächst entschieden. </blockquote>Ich glaube die Tateinheit von Vorratsdatenspeicherung und Suchmaschinen werden uns noch sehr interessante Zeiten bescheren. Insbesondere, wenn die Ermittlungsbehoerden auf die geschilderte Art und Weise arbeiten. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440947" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 26 Dec 2007 07:08:11 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3911-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3911-Himmel.html</feedburner:origLink></item>
<item>
    <title>Dual_EC_DRBG added to Vista SP1</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440948/3895-Dual_EC_DRBG-added-to-Vista-SP1.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3895-Dual_EC_DRBG-added-to-Vista-SP1.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3895</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3895</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Do you remember the <a href="http://www.c0t0d0s0.org/archives/3751-Backdoor.html">article</a> linking to Bruce Schneiers <a onclick="javascript: pageTracker._trackPageview('/extlink/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115');"  href="http://www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115">article about the possible backdoor in the NIST-endorsed Dual_EC_DRBG random number generator</a>. Well exactly this algorithm was added to <a onclick="javascript: pageTracker._trackPageview('/extlink/msdn2.microsoft.com/en-us/library/aa375534.aspx');"  href="http://msdn2.microsoft.com/en-us/library/aa375534.aspx">Microsoft Vista SP1.</a>. As Bruce writes it <a onclick="javascript: pageTracker._trackPageview('/extlink/www.schneier.com/blog/archives/2007/12/dual_ec_drbg_ad.html');"  href="http://www.schneier.com/blog/archives/2007/12/dual_ec_drbg_ad.html">in his blog</a>:<blockquote>t's not enabled by default, and my advice is to never enable it. Ever.</blockquote> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440948" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 18 Dec 2007 14:20:53 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3895-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3895-Dual_EC_DRBG-added-to-Vista-SP1.html</feedburner:origLink></item>
<item>
    <title>CAPTCHAS</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440949/3877-CAPTCHAS.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3877-CAPTCHAS.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3877</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3877</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Interesting <a onclick="javascript: pageTracker._trackPageview('/extlink/www.codinghorror.com/blog/archives/001001.html');"  href="http://www.codinghorror.com/blog/archives/001001.html">article about CAPTCHAs</a>. The author has an interesting metric for the quality of a CAPTCHA ... the price for the software to break it. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440949" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 13 Dec 2007 16:02:00 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3877-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3877-CAPTCHAS.html</feedburner:origLink></item>
<item>
    <title>Scissors would be illegal ..</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440950/3852-Scissors-would-be-illegal-...html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3852-Scissors-would-be-illegal-...html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3852</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3852</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    This presentation explains, why scissors would be illegal, when the DMCA would apply to the the physical world : <a onclick="javascript: pageTracker._trackPageview('/extlink/www.wellingtongrey.net/miscellanea/archive/2007-12-04--DMCA/2007-12-04-on-the-digital-millenium-copyright-act.html');"  href="http://www.wellingtongrey.net/miscellanea/archive/2007-12-04--DMCA/2007-12-04-on-the-digital-millenium-copyright-act.html">The Digital Millenium copyright act -  An Example of Analougue Circumvention and Idiocy</a> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440950" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 08 Dec 2007 14:29:44 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3852-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3852-Scissors-would-be-illegal-...html</feedburner:origLink></item>
<item>
    <title>Vorratsdatenspeicherung - The next generation</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440951/3806-Vorratsdatenspeicherung-The-next-generation.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3806-Vorratsdatenspeicherung-The-next-generation.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3806</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3806</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Wenn Karlsruhe den Politikern irgendwann hoffentlich mal die Sammelwut austreibt, muss die Aufmerksamkeit mal auf die Firmen gelenkt werden, die allzu freizuegig mit Kundeninformation umgehen. Jens von Pixelfeuer (und Sun) schreibt in seinem Blog ueber eine sehr merkwürdige Pressemitteilung von ebay:<a onclick="javascript: pageTracker._trackPageview('/extlink/www.pixelfeuer.de/wp/2007/11/27/mein-kiel-lob-ich-mir-ebay-wertet-aus');"  href="http://www.pixelfeuer.de/wp/2007/11/27/mein-kiel-lob-ich-mir-ebay-wertet-aus">Mein Kiel lob ich mir - Ebay wertet aus</a> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440951" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 27 Nov 2007 13:35:49 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3806-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3806-Vorratsdatenspeicherung-The-next-generation.html</feedburner:origLink></item>
<item>
    <title>Lost</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440952/3781-Lost.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3781-Lost.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3781</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3781</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Okay, it´s a catastrophy when you lose 2 CD with data, but it´s a pattern when you lose CD with sensible data <a onclick="javascript: pageTracker._trackPageview('/extlink/business.timesonline.co.uk/tol/business/money/consumer_affairs/article2917650.ece');"  href="http://business.timesonline.co.uk/tol/business/money/consumer_affairs/article2917650.ece">on a regular basis</a>.  <a onclick="javascript: pageTracker._trackPageview('/extlink/www.theregister.co.uk/2007/11/20/hmrc_loses_lots_data/');"  href="http://www.theregister.co.uk/2007/11/20/hmrc_loses_lots_data/">25 million lost records with bank accounts.</a>. You can only hope that the responsible people were aware of public key cryptography.But ... wait ... i assume <a onclick="javascript: pageTracker._trackPageview('/extlink/www.techworld.com/news/index.cfm?RSS&amp;amp;NewsID=10737');"  href="http://www.techworld.com/news/index.cfm?RSS&amp;NewsID=10737">encrypting the data would cost extra at EDS (like desensitizing)</a>:<blockquote>Sir John Bourn's briefing adds that the reason given in the email - which was copied to an HMRC official at assistant director level - was that desensitising the data would require an extra payment to EDS as it fell outside the scope of EDS's data management contract.</blockquote>And it seems to be a common  pattern. The Daily Mail writes in <a onclick="javascript: pageTracker._trackPageview('/extlink/www.dailymail.co.uk/pages/live/articles/news/news.html?in_article_id=495188&amp;amp;in_page_id=1770');"  href="http://www.dailymail.co.uk/pages/live/articles/news/news.html?in_article_id=495188&amp;in_page_id=1770">Now two MORE discs containing personal data go missing at bungling Ministry of Mayhem</a>:<blockquote>The news comes as it was revealed last night that bungling officials who lost the personal and banking details of everyone who receives child benefit were guilty of more than 2,100 security breaches last year - dragging Gordon Brown to the centre of the shambles.</blockquote>Yet another reason to deny authorities the collection of data. It doesn´t look like they can keep the data for themself ... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440952" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 22 Nov 2007 22:18:41 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3781-guid.html</guid>
    <category>identity</category>
<category>security</category>
<category>uk</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3781-Lost.html</feedburner:origLink></item>
<item>
    <title>Backdoor?</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440953/3751-Backdoor.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3751-Backdoor.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3751</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3751</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Bruce Schneier writes in <a onclick="javascript: pageTracker._trackPageview('/extlink/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115');"  href="http://www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115">"Did NSA Put a Secret Backdoor in New Encryption Standard?"</a>:<blockquote>But today there's an even bigger stink brewing around Dual_EC_DRBG. In an informal presentation (.pdf) at the CRYPTO 2007 conference in August, Dan Shumow and Niels Ferguson showed that the algorithm contains a weakness that can only be described a backdoor.</blockquote>The problem behind cryptographic algorithms is: Can you really trust the inventors of cryptographic mechanisms? Should we only trust cryptographic mechanisms with a long history of scientific discourse? Can you trust cryptographic mechanisms from organisations with the job to know what other people transmit? 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440953" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 16 Nov 2007 20:55:52 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3751-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3751-Backdoor.html</feedburner:origLink></item>
<item>
    <title>Flüssigkeiten im Flieger</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440954/3184-Fluessigkeiten-im-Flieger.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3184-Fluessigkeiten-im-Flieger.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3184</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3184</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Beim <a onclick="javascript: pageTracker._trackPageview('/extlink/vowe.net/archives/008517.html');"  href="http://vowe.net/archives/008517.html">vowe</a> wird in den Kommentaren eine sehr interessante Frage gestellt: In eine volle Blase passen etwa 200-300 ml Flüssigkeit  (laut Wikipedia sind es eher 300-500 ml) rein. Muss man die nicht auch in einer Plastiktüte bei den Sicherheitskontrollen vorzeigen? 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440954" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 12 Jun 2007 07:35:16 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3184-guid.html</guid>
    <category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3184-Fluessigkeiten-im-Flieger.html</feedburner:origLink></item>
<item>
    <title>The number</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440955/3109-The-number.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3109-The-number.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3109</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3109</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    <center><!-- s9ymdb:277 --><img width="400" height="51" style="border: 0px; padding-left: 5px; padding-right: 5px;" src="http://www.c0t0d0s0.org/uploads/thenumber.serendipityThumb.jpg" alt=""  /></center><br />
When you search for a certain sequence of hex digits, you find will 1.32 million hits. The sequence is the processing key for HD-DVD. Even when the MPAA forces Google and Digg to delete all the pages from the indexes or delete all the comments in community forums, those pages must have had millions of pageviews the last few day. Any attempt to delete this key from the internet is senseless. This sequence must be on literally millions of hard discs. <br />
<br />
And to add insult to injury: The hack, that leaded to this sequence hit the HD-DVD at it´s most delicate spot. You can´t revoke the mechanisms without collateral damages. Or as the <a onclick="javascript: pageTracker._trackPageview('/extlink/blog.wired.com/gadgets/2007/02/the_new_hddvdbl.html');"  href="http://blog.wired.com/gadgets/2007/02/the_new_hddvdbl.html">Wired Gadget Lab Blog writes</a>:<blockquote>How might the companies respond? The processing key can now be changed for future disks. However, the flaws inherent in the system make it appear easy to discover the replacement: the method of attack itself will be hard to offset without causing knock-on effects. For example, revoking player keys (in advance of obfuscating the keys in memory in future revisions of the system) would render current players unable to view future movies. Revoking the volume and processing keys that have been hacked would mean that all movies to date would not run on new players.</blockquote> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440955" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sun, 06 May 2007 16:45:51 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3109-guid.html</guid>
    <category>hd-dvd</category>
<category>security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3109-The-number.html</feedburner:origLink></item>
<item>
    <title>Least secured system</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440956/3073-Least-secured-system.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/3073-Least-secured-system.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=3073</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=3073</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    One additional <a href="http://www.c0t0d0s0.org/archives/3058-Breachable-virtual-machines.html">thought</a>: Whenever an exploit against an hypervisor technology gets available, the least secured system compromises the security of all systems on the respective hardware. And as all virtual machines are independent kernel and operating system images, you will have a tough time time consistently secure your system. And the problem gets more severe, when multiple independent customers share a system. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440956" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 26 Apr 2007 16:24:05 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/3073-guid.html</guid>
    <category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/3073-Least-secured-system.html</feedburner:origLink></item>
<item>
    <title>What have we learned from history?</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440957/2851-What-have-we-learned-from-history.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2851-What-have-we-learned-from-history.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2851</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2851</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    <center><a onclick="javascript: pageTracker._trackPageview('/extlink/www.youtube.com/watch?v=Xs3SfNANtig');"  class='serendipity_image_link' href='http://www.youtube.com/watch?v=Xs3SfNANtig' target="_blank"><!-- s9ymdb:243 --><img width="466" height="353" style="border: 0px; padding-left: 5px; padding-right: 5px;" src="http://www.c0t0d0s0.org/uploads/trojan.jpg" alt=""  /></a><br />
<small>(click <a onclick="javascript: pageTracker._trackPageview('/extlink/www.youtube.com/watch?v=Xs3SfNANtig');"  class='serendipity_image_link' href='http://www.youtube.com/watch?v=Xs3SfNANtig' target="_blank">here to view view</a>)</small></center><br />
<br />
Obviously: <b>Nothing!</b><br />
<br />
Update: The video was removed from Youtube. The reason: Copyright violation. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440957" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 07 Mar 2007 20:29:29 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2851-guid.html</guid>
    <category>security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2851-What-have-we-learned-from-history.html</feedburner:origLink></item>
<item>
    <title>The desperate need for deniable encryption</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440958/2831-The-desperate-need-for-deniable-encryption.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2831-The-desperate-need-for-deniable-encryption.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2831</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2831</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    There is a good reason to develop <a onclick="javascript: pageTracker._trackPageview('/extlink/en.wikipedia.org/wiki/Deniable_encryption');"  href="http://en.wikipedia.org/wiki/Deniable_encryption">Deniable Encryption</a>. According to a blog entry of <a onclick="javascript: pageTracker._trackPageview('/extlink/blog.fefe.de/?ts=bb19e534');"  href="http://blog.fefe.de/?ts=bb19e534">fefe</a> US law enforcement agencies are allowed to copy your harddisk and to demand to get the passwords for encrypted files when you want to enter the US.  Reportedly the border control is authorized to put you in coercive detention to gather the password.<br />
<br />
So you need an encryption, that is not detectable or you need two notebooks. One you use to store your confidential data and one sanitized from all confidential data  with only the files you need while you visit the US. <br />
<br />
PS: Well, nice sideeffect,  it would be very easy to put someone into long detention: Send him a long encrypted mail. But encrypt it with a secret key unknown to the person <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/wink.png" alt=";-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440958" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 02 Mar 2007 22:24:59 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2831-guid.html</guid>
    <category>security</category>
<category>travel</category>
<category>us</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2831-The-desperate-need-for-deniable-encryption.html</feedburner:origLink></item>
<item>
    <title>US-VISIT</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440959/2788-US-VISIT.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2788-US-VISIT.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2788</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2788</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    When you want to enter the US, you get processed by the US-VISIT system. Two fingerprints and a photo are taken from you. From my view, it´s something like a accounting system for visitors. To state it simple: you check in to the US and you check out of the US. In principle you know, how many and which visitors are in the country. Sounds good. But in fact, the reality isn´t always cute to such simple thoughts: In an <a onclick="javascript: pageTracker._trackPageview('/extlink/searching.gao.gov/cs.html?charset=iso-8859-1&amp;amp;url=http%3A//www.gao.gov/new.items/d07499t.pdf&amp;amp;qt=US-VISIT&amp;amp;col=audprod+legal&amp;amp;n=1&amp;amp;la=en');"  href="http://searching.gao.gov/cs.html?charset=iso-8859-1&amp;url=http%3A//www.gao.gov/new.items/d07499t.pdf&amp;qt=US-VISIT&amp;col=audprod+legal&amp;n=1&amp;la=en">report of the Government Accountability Office</a> several problems with this system were reported, ranging from organisatorical and technological problems with it.<br />
<br />
My personal conclusions from this story: <br />
<ul><li>You can´t buy security, even billions of dollar are incapable to this job.</li><li>Technology will leave you alone on half way, when you expect perfection. Technology is designed with defined limitations and capabilities. When you are not able to control the circumstances to be perfectly in your specification you are essentially toast (for example: How do you ensure, that an RFID´ed passport leaves the country with the person</li></ul> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440959" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 21 Feb 2007 13:49:57 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2788-guid.html</guid>
    <category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2788-US-VISIT.html</feedburner:origLink></item>
<item>
    <title>Internet Explorer</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440960/2765-Internet-Explorer.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2765-Internet-Explorer.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2765</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2765</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    At last: The PCWorld writes, what almost everybody thinks: <a onclick="javascript: pageTracker._trackPageview('/extlink/www.pcworld.com/article/id,128538/article.html?tk=nl_spxhow');"  href="http://www.pcworld.com/article/id,128538/article.html?tk=nl_spxhow">IE is the biggest security threat in 2007</a>. Well, i would add ... in 2006, in 2005, in 2003, in 2002 ..... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440960" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 15 Feb 2007 22:59:33 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2765-guid.html</guid>
    <category>security</category>
<category>windows</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2765-Internet-Explorer.html</feedburner:origLink></item>
<item>
    <title>Purer, unverhüllter Neid</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440961/2759-Purer,-unverhuellter-Neid.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2759-Purer,-unverhuellter-Neid.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2759</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2759</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Bei mir ist ja gestern abend noch der blanke Neid ausgebrochen. Und ich war noch nicht mal unschuldig an den Gedankengängen, die letztlich dazu geführt haben. Via ICQ hat mich eine befreundete Administratorin angeschrieben und mir freudestrahlend erzählt, das sämtliche Windows-Notebooks ausgephased werden und durch MacBook´s und MacBook Pros ersetzt werden. Warum? Erheblich einfacher zu warten und vor allen Dingen man schmeisst nicht allerlei Firmen nicht noch Geld in den Rachen, um das Betriebsystem halbwegs abzusichern (Virenscanner, Firewall, Malwarescanner, Majorfuckupinbrain-Scanner). <br />
<br />
Warum ich da nicht dran unschuldig war? Ich hatte Ihr in letzter Zeit häufiger Links zum Ärgern zukommen lassen: Beispielsweise die Story, das <a href="http://www.c0t0d0s0.org/archives/2520-284-Tage.html">284 Tage im letzten Jahr unpatchbar unsicher war</a>, weil es schlicht gegen bestimmte Bugs keine Patches gab. Oder das XP bei einem Test im Netz ohne zusätzliche Schutzprogramme keine 10 Sekunden hielt, bevor es gehackt wurde (Link ist mir gerade abhanden gekommen). Ich wollte dann noch <a onclick="javascript: pageTracker._trackPageview('/extlink/theinvisiblethings.blogspot.com/2007/02/vista-security-model-big-joke.html');"  href="http://theinvisiblethings.blogspot.com/2007/02/vista-security-model-big-joke.html">"Vista Security Model  A Big Joke?"</a> von Frau Rutkowska rüberschicken, aber da kam man mir bereits mit der Antwort zuvor, das man dafür eine anständige Lösung hätte. Und da war er dann da: Der Neid. Naja, ich warte noch bis zum nächsten Mac Book Pro, dann wird der Neid auch erstmal wieder gestillt, wenn ich Nutzer des aktuellen MBP sehe. <br />
<br />
PS: Leider habe ich es nicht geschafft, sie von Solaris auf den Notebooks zu überzeugen. Sie weiss, das ich MacOS X für den momentan besten Desktop halt. Wenn ich selbst Solaris nicht auf dem Notebook nutze, dann kann ich es verstehen, das Freunde es dann auch nicht tun. Aber hey, sicherer als das Betriebsystem aus Redmond ist Mac OS X allemal. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440961" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 15 Feb 2007 07:47:52 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2759-guid.html</guid>
    <category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2759-Purer,-unverhuellter-Neid.html</feedburner:origLink></item>
<item>
    <title>Security in der Security Branche</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440962/2740-Security-in-der-Security-Branche.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2740-Security-in-der-Security-Branche.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2740</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2740</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Wahrscheinlich sollte man schleunigst Reissaus nehmen, wenn jemand Security Consultant auf der Visitenkarte stehen hat. Sowieso, wenn er oder sie Konferenzen besucht: <a onclick="javascript: pageTracker._trackPageview('/extlink/news.yahoo.com/s/pcworld/128921');"  href="http://news.yahoo.com/s/pcworld/128921">Conference Attendees Drop Ball on Wi-Fi Security</a> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440962" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sun, 11 Feb 2007 19:41:59 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2740-guid.html</guid>
    <category>security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2740-Security-in-der-Security-Branche.html</feedburner:origLink></item>
<item>
    <title>284 Tage</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440963/2520-284-Tage.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2520-284-Tage.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2520</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2520</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Man kann sich bei dieser Zahl mehrere Dinge fragen: Warum vertraut noch irgendjemand Microsoft? Zumindestens in soweit, <a onclick="javascript: pageTracker._trackPageview('/extlink/www.heise.de/security/artikel/82780');"  href="http://www.heise.de/security/artikel/82780">als das man sich dafür PR macht</a>? Was ist so schwer daran, einen Browser halbwegs sicher zu halten? Microsoft hat doch Connectix samt VirtualPC gekauft. Warum verwenden sie das nicht als Lösung, um ihren ganzen Internet Explorer/Outlook-Unsicherheitskomplex in einer Sandbox laufen zu lassen. Nach Benutzung die Sandbox ausleeren und neuen Sand, ähm ein neues Windows rein. Warum gibt es immer noch Applikationen, die zwingend den Internet Explorer voraussetzen.<br />
<br />
Und jeder der glaubt, das das Sicherheitsproblem schon nicht so schlimm sei, möge sich bitte diesen Artikel durchlesen:<a onclick="javascript: pageTracker._trackPageview('/extlink/blog.washingtonpost.com/securityfix/2007/01/internet_explorer_unsafe_for_2.html');"  href="http://blog.washingtonpost.com/securityfix/2007/01/internet_explorer_unsafe_for_2.html">Internet Explorer Unsafe for 284 Days in 2006</a>. An 284 Tagen gab es für bekannte Sicherheitslücken keine Bugfixes. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440963" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 08 Jan 2007 08:33:57 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2520-guid.html</guid>
    <category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2520-284-Tage.html</feedburner:origLink></item>
<item>
    <title>Don´t blur!</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440964/2517-Dont-blur!.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2517-Dont-blur!.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2517</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2517</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Interessanter Text über eine eine Wörterbuchattacke gegen unkenntlich gemachte Zahlenkombinationen: <a onclick="javascript: pageTracker._trackPageview('/extlink/dheera.net/projects/blur.php');"  href="http://dheera.net/projects/blur.php">Why blurring sensitive information is a bad idea!</a>. Zusammenfassend: Eine Unkenntlichmachung, die auf einem Algorithmus basiert, kann möglicherweise ausgehebelt werden. Lösung ist allerdings einfach: Schwarzen einfarbigen Block drüber. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440964" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 08 Jan 2007 01:34:06 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2517-guid.html</guid>
    <category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2517-Dont-blur!.html</feedburner:origLink></item>
<item>
    <title>The problems of Vista Content Protection</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440965/2442-The-problems-of-Vista-Content-Protection.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2442-The-problems-of-Vista-Content-Protection.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2442</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2442</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    <a onclick="javascript: pageTracker._trackPageview('/extlink/www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt');"  href="http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt">Peter Gutmann</a> wrote an excellent essay about the costs of the content protection in Vista, that we even incur when we plan <b>not</b> to use Vista.<br />
<br />
<blockquote> This document analyses the cost involved in Vista's content protection, and the collateral damage that this incurs throughout the computer industry.</blockquote>and<blockquote>Here's an offer to Microsoft: If we, the consumers, promise to never, ever, ever buy a single HD-DVD or Blu-Ray disccontaining any precious premiumcontent [Note E], will you in exchange withhold this poison from the computer industry?  Please?</blockquote><br />
 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440965" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 25 Dec 2006 11:04:12 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2442-guid.html</guid>
    <category>drm</category>
<category>microsoft</category>
<category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2442-The-problems-of-Vista-Content-Protection.html</feedburner:origLink></item>
<item>
    <title>Bruce Schneier on Spam</title>
    <link>http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~3/316440966/2384-Bruce-Schneier-on-Spam.html</link>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/2384-Bruce-Schneier-on-Spam.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=2384</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=2384</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Bruce Schneier wrote an interesting article about Spam: <a onclick="javascript: pageTracker._trackPageview('/extlink/www.forbes.com/security/2006/12/11/spam-security-email-tech-security-cz_bs_1212spam.html');"  href="http://www.forbes.com/security/2006/12/11/spam-security-email-tech-security-cz_bs_1212spam.html">Why Spam Won't Go Away</a>. Spam and spam protection is the same like designing an unbreachable armor. You are save for a while, but the bullet designers wins at the end at any case. Thus the only way to stop the arms race is making the bullet more expensive than the wins you get by using the bullet. But before this happens Microsoft should stop to produce a ricochet generating operating system making blacklisting almost useless. <br />
Perhaps the spam can only prevented by the same tactics spammers use: Distributed attack mitigation against distributed spam fanouts. A user generated whitelist based on a web of trust.  People in my own address book are trusted sender of mail,  the people in the address book of my contact are half trusted sender and so on. And people or senders marked as Spammers in my address book are 100% malicious, people or systems in spam lists are 50% malicious. If the trust value or malicious value is above 51% the mail gets the "ham" tag, below this value it´s tagged as spam. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/316440966" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 13 Dec 2006 09:36:00 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/2384-guid.html</guid>
    <category>Security</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/2384-Bruce-Schneier-on-Spam.html</feedburner:origLink></item>

</channel>
</rss>
