<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><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.5.5 - http://www.s9y.org/</generator>
    
    

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/C0t0d0s0org-Security" /><feedburner:info uri="c0t0d0s0org-security" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
    <title>Protecting your data with two factors and ZFS dataset encryption</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/7lBdS1fDUlc/7055-Protecting-your-data-with-two-factors-and-ZFS-dataset-encryption.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
    
    <comments>http://www.c0t0d0s0.org/archives/7055-Protecting-your-data-with-two-factors-and-ZFS-dataset-encryption.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7055</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=7055</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    It's really easy to use ZFS dataset encryption to protect your data in a way so you have to know something and to own something to get access to encrypted data. <br /><a href="http://www.c0t0d0s0.org/archives/7055-Protecting-your-data-with-two-factors-and-ZFS-dataset-encryption.html#extended">Continue reading "Protecting your data with two factors and ZFS dataset encryption"</a>
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/7lBdS1fDUlc" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 23 Nov 2010 08:01:05 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7055-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7055-Protecting-your-data-with-two-factors-and-ZFS-dataset-encryption.html</feedburner:origLink></item>
<item>
    <title>Darren Moffat about the internals of ZFS encryption</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/O-UFxLi8FYM/7052-Darren-Moffat-about-the-internals-of-ZFS-encryption.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/7052-Darren-Moffat-about-the-internals-of-ZFS-encryption.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7052</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=7052</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Darren Moffat wrote a great blog article about the internals of the ZFS encryption - <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.sun.com/darren/entry/zfs_encryption_what_is_on']);"  href="http://blogs.sun.com/darren/entry/zfs_encryption_what_is_on">"ZFS encryption what is on disk ?"</a>:<blockquote>This article is about what is and isn't stored encrypted on disk for ZFS datasets that are encrypted and how we do the actual encryption. It does require some understanding of Solaris and ZFS debugging tools.</blockquote> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/O-UFxLi8FYM" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 19 Nov 2010 22:22:31 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7052-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7052-Darren-Moffat-about-the-internals-of-ZFS-encryption.html</feedburner:origLink></item>
<item>
    <title>Darren Moffat about ZFS encryption</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/bwnIuhXUZek/7034-Darren-Moffat-about-ZFS-encryption.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/7034-Darren-Moffat-about-ZFS-encryption.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=7034</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=7034</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Darren wrote three really interesting articles about ZFS encryption: The first one is <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.sun.com/darren/entry/introducing_zfs_crypto_in_oracle']);"  href="http://blogs.sun.com/darren/entry/introducing_zfs_crypto_in_oracle">Introducing ZFS Crypto in Oracle Solaris 11 Express</a>. This blog entry gives you a first overview how to use encryption for ZFS datasets. The second one titled <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.sun.com/darren/entry/assued_delete_with_zfs_dataset']);"  href="http://blogs.sun.com/darren/entry/assued_delete_with_zfs_dataset">"Assured delete with ZFS dataset encryption"</a> explains how you can use the encryption feature to implement <a href="http://www.c0t0d0s0.org/permalink/Secure-Deletion-with-ZFS.html">assured deletion</a> with the "throwing the keys away" technique. Last but not least the article <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.sun.com/darren/entry/compress_encrypt_checksum_deduplicate_with']);"  href="http://blogs.sun.com/darren/entry/compress_encrypt_checksum_deduplicate_with">"Having my secured cake and Cloning it too (aka Encryption + Dedup with ZFS)"</a> explains how deduplication and encryption work together in Solaris 11 Express. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/bwnIuhXUZek" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 16 Nov 2010 08:50:43 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/7034-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/7034-Darren-Moffat-about-ZFS-encryption.html</feedburner:origLink></item>
<item>
    <title>Performance Impact of kssl</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/bB73UPOZA-Q/6926-Performance-Impact-of-kssl.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/6926-Performance-Impact-of-kssl.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=6926</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=6926</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    One of the hidden gem of Solaris is the kssl feature. Long-time readers know this feature, as i wrote a <a href="http://www.c0t0d0s0.org/archives/5575-Less-known-Solaris-Features-kssl.html">tutorial about it</a>. For the uninitiated: It's a in-kernel SSL proxy. Why should you put this in the kernel. Well, especially when you use a SSL-accelerator you have to jump from user space to kernel space and back several times as the SSL library (OpenSSL e.g) is in user space and the driver for the card is in kernel space. That jumping costs you a lot of time. There is an interesting <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.sun.com/BestPerf/entry/20100920_sparc_t3_weblogic_security']);"  href="http://blogs.sun.com/BestPerf/entry/20100920_sparc_t3_weblogic_security">article about Weblogic SSL performance</a> in the BestPerf blog.<br />
<br />
When you just want to take one thing out of this whole article, then just look at the first chart at the red and the blue line: Red is the system configured to provide SSL via kssl, blue is the system configured to provide SSL via Weblogic itself. Both systems are using the SSL hardware. I don't know how you would call it, but the difference is pretty significant. A good example, why kssl is such a nice tool. And it's just there in Solaris 10. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/bB73UPOZA-Q" height="1" width="1"/>]]></content:encoded>

    <pubDate>Fri, 24 Sep 2010 21:50:49 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/6926-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/6926-Performance-Impact-of-kssl.html</feedburner:origLink></item>
<item>
    <title>Tracking via Bluetooth</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/Rt6y85tmVII/6440-Tracking-via-Bluetooth.html</link>
            <category>Aviation</category>
            <category>English</category>
            <category>Privacy</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/6440-Tracking-via-Bluetooth.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=6440</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=6440</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    The german IT news portal Heise linked to an interesting paper: <a onclick="_gaq.push(['_trackPageview', '/download/ftp://ftp.ecn.purdue.edu/darcy/IND/10-1438_ind_2009_11_14.pdf']);"  href="ftp://ftp.ecn.purdue.edu/darcy/IND/10-1438_ind_2009_11_14.pdf">"Anonymous Bluetooth Probes for Measuring Airport Security Screening Passage Time: The Indianapolis Pilot Deployment"</a>.<br />
<br />
An interesting concept: Anybody who just start the Bluetooth scan on her/his notebook knows that there are several mobile phones on almost any given location with a large audience propagating a unique id to the world by their MAC address. Using this information to derive some useful facts from it (for example: Duration of the average TSA massage) looks like as one of the more worthy targets for tradeoffs on privacy vs. useful services in favor to the second one. Especially as it's really easy to evade from this data collection: Just switch off the bluetooth function of your mobile. <br />
<br />
PS: I would like a bluetooth scanner in the aircraft itself ... it's really interesting how many mobile phones are running inflight.  Such a scanner could send a vcard containing "Just switch off your fscking mobile phone". Did that once a few minutes before takeoff ... that was very effective <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/Rt6y85tmVII" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 24 Mar 2010 23:02:46 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/6440-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/6440-Tracking-via-Bluetooth.html</feedburner:origLink></item>
<item>
    <title>Somewhat paranoid.</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/8oLM7ljvLZE/6351-Somewhat-paranoid..html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/6351-Somewhat-paranoid..html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=6351</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=6351</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    There was some discussion about possible attack vectors for checksum-only deduplication. However i don't think the proposed vectors are really feasible. The first attack tries to create data corruption by foiling deduplication into using a thoughtfully created block, with the same checksum but different data. Another, less discussed attack vector, is gaining knowledge of a block by using a thoughtfully created block to foil dedup to show you a different block than the one you have actually written, as the checksum-only variant didn't stored your block, but just created a pointer to data written beforehand. <br /><a href="http://www.c0t0d0s0.org/archives/6351-Somewhat-paranoid..html#extended">Continue reading "Somewhat paranoid."</a>
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/8oLM7ljvLZE" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sun, 07 Feb 2010 07:51:28 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/6351-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/6351-Somewhat-paranoid..html</feedburner:origLink></item>
<item>
    <title>Scientist fools nude scanner</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/1STwOV34FGc/6278-Scientist-fools-nude-scanner.html</link>
            <category>English</category>
            <category>Privacy</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/6278-Scientist-fools-nude-scanner.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=6278</wfw:comment>

    <slash:comments>5</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=6278</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    This is a nice example, why those backscatter airport scanners are not the solution of all problems in airport security. The interesting part starts at 18:05 of  <a onclick="_gaq.push(['_trackPageview', '/extlink/www.zdf.de/ZDFmediathek/beitrag/video/942976/Wie-funktioniert-der-Koerperscanner%253F#/beitrag/video/942976/Wie-funktioniert-der-Koerperscanner%3F']);"  href="http://www.zdf.de/ZDFmediathek/beitrag/video/942976/Wie-funktioniert-der-Koerperscanner%253F#/beitrag/video/942976/Wie-funktioniert-der-Koerperscanner%3F">this video</a> available in the ZDF mediathek (an public broadcasting network in Germany). Despite being scanned they are not able to find the thermite the scientist is carrying. The guy demoing the scanner doesn't look amused as well as Mr. Bosbach, a german politician who thinks that we should use such scanners, if they are able to protect the privacy of the scanned peoples. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/1STwOV34FGc" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 14 Jan 2010 19:40:45 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/6278-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/6278-Scientist-fools-nude-scanner.html</feedburner:origLink></item>
<item>
    <title>Apropos nude scanning and the media</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/gbJJSbweCXI/6253-Apropos-nude-scanning-and-the-media.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/6253-Apropos-nude-scanning-and-the-media.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=6253</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=6253</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    It turned out that the images of a story about "What a nude scanner" in germanys favorite gossip catapult and tabloid were faked: BildBlog - a watchblog dedicated to this tabloid - reports in <a onclick="_gaq.push(['_trackPageview', '/extlink/feedproxy.google.com/~r/bildblog/~3/oIImuoI91g8/']);"  href="http://feedproxy.google.com/~r/bildblog/~3/oIImuoI91g8/">"Kehraus 2009"</a> that this newspaper just used a "Negative" plugin of their favorite photo alteration application to create such photos from a cd containing photos of a nude woman... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/gbJJSbweCXI" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 04 Jan 2010 12:59:07 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/6253-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/6253-Apropos-nude-scanning-and-the-media.html</feedburner:origLink></item>
<item>
    <title>Nude scanners revisited - again</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/0GoBhqxEK8s/6252-Nude-scanners-revisited-again.html</link>
            <category>English</category>
            <category>policy of ...</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/6252-Nude-scanners-revisited-again.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=6252</wfw:comment>

    <slash:comments>6</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=6252</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    There is a lot of discussion about the backscatter scanners (or as the media calls them: "nude scanners") in Germany at the moment. Technically it's in discussion for a long time. I wrote <a onclick="_gaq.push(['_trackPageview', '/extlink/www.moellenkamp.org/archives/777-Maximal-invasive-Sicherheit.html']);"  href="http://www.moellenkamp.org/archives/777-Maximal-invasive-Sicherheit.html">about it in 2005 after Bruce Schneier wrote about it</a>. My thought at this moment was "Okay, they will need an aircraft blown out of the sky to force this into the public".<br />
<br />
Personally i think the this is lobby at work at the moment. It's a big business to implement backscatter at all airports in germany alone. Just think about the central security area in Hamburg.10 entries ... ka-ching .... and Hamburg is a relatively small airport. <br />
<br />
At first: I have no problem with backscatter scanning. Technically the current metal detectors look through my clothing as well. So if a backscatter scanner makes no images and instead just make "boink" (as we all know, <a onclick="_gaq.push(['_trackPageview', '/extlink/www.amazon.de/gp/product/0836218787?ie=UTF8&amp;amp;tag=wwwc0t0d0s0or-21&amp;amp;linkCode=as2&amp;amp;camp=1638&amp;amp;creative=19454&amp;amp;creativeASIN=0836218787']);"  href="http://www.amazon.de/gp/product/0836218787?ie=UTF8&amp;tag=wwwc0t0d0s0or-21&amp;linkCode=as2&amp;camp=1638&amp;creative=19454&amp;creativeASIN=0836218787">scientific progress goes "boink"</a><img src="http://www.assoc-amazon.de/e/ir?t=wwwc0t0d0s0or-21&l=as2&o=3&a=0836218787" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" />) and then get a <a href="http://www.c0t0d0s0.org/archives/5023-Air-travellers-euphemism.html">TSA massage</a>, i'm fine with that. <br />
<br />
I'm not fine with high resolution nude photos of every one just want to fly, i'm not fine with spending millions for back scatter scanners, while the people at security can decide to flip burgers or searching people at almost the same wage, i'm not fine with dumbed down version of this scanners with software to protect the privacy as the bad-guys will find ways to use this dumbing-down to fool this device (i want just simple logic .. there is something else than your leather underpants or your latex bra under your clothing .... "boink" -> TSA massage). I'm not fine with with maximal invasive security counter measures, that just helps against past attacks, but not against future attacks. <br />
<br />
The same politicians that force us into this back scatter scannings will be the first ones that will cry when the "Bild Zeitung" will publish the length of their private parts. Who prevents someone who can flip burgers for the same wage to get bribed for not seeing a bomb in his or her shift or for writing down interesting information about prominent people. In former times we used well-paid public servant for this task to reduce this risk ... but today. <br />
<br />
And at the end those back scatter scanning is somehow futile anyways: Drug dealers found out that it's quite simple to hide drugs inside a person. Backscatter can't detect it, as it stops at the first layer of the skin. So what's the problem to substitute the cocaine with Semtex to create a not-so-intelligent bomb?<br />
<br />
 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/0GoBhqxEK8s" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 04 Jan 2010 10:48:15 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/6252-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/6252-Nude-scanners-revisited-again.html</feedburner:origLink></item>
<item>
    <title>Webseminar "Solaris 10 Security" mit Tonspur</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/ojSNArU4pgs/6014-Webseminar-Solaris-10-Security-mit-Tonspur.html</link>
            <category>German</category>
            <category>Security</category>
            <category>Solaris</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/6014-Webseminar-Solaris-10-Security-mit-Tonspur.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=6014</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=6014</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Gestern lief das Webseminar "Solaris 10 Security". Dieses möchte ich Euch nun als <a onclick="_gaq.push(['_trackPageview', '/extlink/blip.tv/file/2719945']);"  href="http://blip.tv/file/2719945">Video</a> zur Verfügung stellen:<br />
<br />
<center><a onclick="_gaq.push(['_trackPageview', '/extlink/blip.tv/file/2719945']);"  class='serendipity_image_link' href='http://blip.tv/file/2719945'><!-- s9ymdb:658 --><img class="serendipity_image_center" width="400" height="235" style="border: 0px; padding-left: 5px; padding-right: 5px;" src="http://www.c0t0d0s0.org/uploads/solaris10.serendipityThumb.png" alt=""  /></a></center><br />
Ich hoffe es ist informativ für Euch. Der CC-Teil am Anfang ist etwas vereinfacht für Einsteiger in die Thematik. Ich möchte mich bei <a onclick="_gaq.push(['_trackPageview', '/extlink/twitter.com/ahu_censhare/statuses/4869656773']);"  href="http://twitter.com/ahu_censhare/statuses/4869656773">einem der Zuhörer</a> für die freundliche Zurverfügungstellung der Aufzeichnung bedanken, nachdem das im Tool selber nicht funktionierte. Vielen Dank! <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/ojSNArU4pgs" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 14 Oct 2009 18:34:15 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/6014-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/6014-Webseminar-Solaris-10-Security-mit-Tonspur.html</feedburner:origLink></item>
<item>
    <title>Frustrated, really frustrated</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/t2vA6BbDRmk/5970-Frustrated,-really-frustrated.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5970-Frustrated,-really-frustrated.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5970</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5970</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    I'm really frustrated at the moment. My second webseminar "Solaris Security" was scheduled for today. We use WebEx for our presentations, so you use a java tool for the slides and use the ordinary telephone for the audio track of the presentation. Everything went well ... until some minutes into the presentation. I was thrown out of the telephone conference. I've noticed this situation 10 minutes later, so i've talked with the void for quite a while. I wasn't able to get back. I've tried with the fixed line, with my job cell phone, even with my private cell phone. But no chance. I wasn't able to get back into the call.  At the end we stopped the call. In the hindsight the signs were on the wall, because there were significantly less users in the telephone conference than in related the WebEx tool session right from the start.<br />
<br />
We have a new time for the call: 13.10.2009 from 14pm to 15pm. Sorry for any inconvenience. But this give others the chance to attend the meeting: So if you haven't been able to register for the event today, you can use <a onclick="_gaq.push(['_trackPageview', '/extlink/dct.sun.com/dct/forms/reg_de_2307_986_0.jsp']);"  href="https://dct.sun.com/dct/forms/reg_de_2307_986_0.jsp">the old form to register for the new date</a>. Everyone else should already have the mail with the details for the next event.<br />
<br />
PS: I've checked the Webex voice numbers a few minutes ago .. still broken ... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/t2vA6BbDRmk" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 30 Sep 2009 15:16:50 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5970-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5970-Frustrated,-really-frustrated.html</feedburner:origLink></item>
<item>
    <title>Presentation</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/dkN26WrZigU/5967-Presentation.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5967-Presentation.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5967</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5967</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    I've finalized the presentation i want to hold tomorrow. In a series of web seminars in german language i'm presenting on Solaris Security tomorrow afternoon. I don't think i will put the german version online at my own blog, but i'm thinking about an english version. I just integrated a short chapter about the <a onclick="_gaq.push(['_trackPageview', '/extlink/kenai.com/projects/isc/pages/Home']);"  href="http://kenai.com/projects/isc/pages/Home">Immutable Service Container</a>. This is really an interesting concept introduced by Glen Brunette. But i have just an hour. So many topics and not enough time. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/dkN26WrZigU" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 29 Sep 2009 20:31:35 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5967-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5967-Presentation.html</feedburner:origLink></item>
<item>
    <title>Not-so-smart bombs</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/lB0jmES6vMk/5962-Not-so-smart-bombs.html</link>
            <category>English</category>
            <category>Privacy</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5962-Not-so-smart-bombs.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5962</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5962</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Whenever a friend asks me about a tip in regard of flying and getting rid of the fear of flying a give them some hints and at the end i make the joke "Oh, and then there are the people who ask you friendly to bend over while thy putting on a latex glove. Just relax". All muscles of the face just go south and the reactions are  just to funny to leave out this joke. Just be sure, that you don't start to smile <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/wink.png" alt=";-)" style="display: inline; vertical-align: bottom;" class="emoticon" /><br />
<br />
The problem: I don't think that using a plane will be fun, when you think about the implications of the latest attack on a saudi prince: <a onclick="_gaq.push(['_trackPageview', '/extlink/www.khaleejtimes.com/DisplayArticleNew.asp?col=&amp;amp;section=opinion&amp;amp;xfile=data/opinion/2009/September/opinion_September25.xml']);"  href="http://www.khaleejtimes.com/DisplayArticleNew.asp?col=&amp;section=opinion&amp;xfile=data/opinion/2009/September/opinion_September25.xml">The assassin had the bomb inside of his body ... to be exact ... in his colon</a>. That's looks to be the newest fashion in not-so-smart bomb technology. With George W. Bush i would be sure, that would lead to rectal probing for everyone. With Obama i have some hope, that they won't go <strong>this</strong> far. Perhaps we just see an increased rate of radiation induced cancer due to mandatory X-ray examinations at the airport, because the backscatter scanners (we call them "nude scanner" in Germany) are not capable to look into a body, just under the clothes. <br />
<br />
PS: I don't know what Mr. Schaeuble will do in regard of this. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/lB0jmES6vMk" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sun, 27 Sep 2009 10:05:49 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5962-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5962-Not-so-smart-bombs.html</feedburner:origLink></item>
<item>
    <title>Guide to AES</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/zj6OMb-fOfk/5961-Guide-to-AES.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Technology</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5961-Guide-to-AES.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5961</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5961</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    The cryptographic algorithm AES is everywhere. You find it in your router, you find in your OS. Your WiFi  network use it. And probably the three-letter agency in your country,too . But how does it works? Jeff Moser wrote (well, it's more a comic) the <a onclick="_gaq.push(['_trackPageview', '/extlink/www.moserware.com/2009/09/stick-figure-guide-to-advanced.html']);"  href="http://www.moserware.com/2009/09/stick-figure-guide-to-advanced.html">"Stick Figure Guide to the Advanced Encryption Standard (AES)"</a>. A really great explanation of AES. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/zj6OMb-fOfk" height="1" width="1"/>]]></content:encoded>

    <pubDate>Sat, 26 Sep 2009 10:40:53 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5961-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5961-Guide-to-AES.html</feedburner:origLink></item>
<item>
    <title>Nice usecase for ZFS</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/VEgkKkIWBoc/5903-Nice-usecase-for-ZFS.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5903-Nice-usecase-for-ZFS.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5903</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5903</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    The Apache Foundation had a <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.apache.org/infra/entry/apache_org_downtime_initial_report']);"  href="https://blogs.apache.org/infra/entry/apache_org_downtime_initial_report">security breach a few days ago</a> (no, not on the Solaris 10 system <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/wink.png" alt=";-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> ), that led to the compromitation of their services.  A nice information was the role that ZFS played in the recovery of this situation. The Infastructure Team wrote in their article <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.apache.org/infra/entry/apache_org_downtime_report']);"  href="https://blogs.apache.org/infra/entry/apache_org_downtime_report">about the recovery</a>:<blockquote>aurora.apache.org runs Solaris 10, and we were able to restore the box to a known-good configuration by cloning and promoting a ZFS snapshot from a day before the CGI scripts were synced over. Doing so enabled us to bring the EU server back online, and to rapidly restore our main websites. Thereafter, we continued to analyze the cause of the breach, the method of access, and which, if any, other machines had been compromised.</blockquote> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/VEgkKkIWBoc" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 07 Sep 2009 21:51:37 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5903-guid.html</guid>
    <category>solaris</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5903-Nice-usecase-for-ZFS.html</feedburner:origLink></item>
<item>
    <title>FIPS 140-2 Sec Level 2 for Sun Tape drive</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/FgOI3rcqDDA/5873-FIPS-140-2-Sec-Level-2-for-Sun-Tape-drive.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Sun/Oracle</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5873-FIPS-140-2-Sec-Level-2-for-Sun-Tape-drive.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5873</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5873</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Perhaps that's interesting for people needing a highly secure tape storage. As reported <a onclick="_gaq.push(['_trackPageview', '/extlink/www.eweek.com/c/a/Data-Storage/Sun-Earns-Federal-Encryption-Certification-for-StorageTek-Tape-Platform-224039/?kc=rss']);"  href="http://www.eweek.com/c/a/Data-Storage/Sun-Earns-Federal-Encryption-Certification-for-StorageTek-Tape-Platform-224039/?kc=rss">by eWeek</a> the StorageTek T10000B tape drive got the FIPS 140-2 certification:<blockquote>Nonetheless, Sun revealed Aug. 19 that it has become the first enterprise tape drive maker to be granted a prestigious federal security qualification: the FIPS 140-2 Certification at Security Level 2 for its Sun StorageTek T10000B tape drive.</blockquote>The T10000B drive has the integrated capability to encrypt the data before writing it to the tape. Thus it contains components to do this encryption. The FIPS certification states that a hardware device complies to the standards set by the FIPS 140-2 document, which is headlined "Security Requirements for Cryptographic Modules".  A level 2 FIPS certification means (copied from the Wikipedia <a onclick="_gaq.push(['_trackPageview', '/extlink/en.wikipedia.org/wiki/FIPS_140-2#Level_2']);"  href="http://en.wikipedia.org/wiki/FIPS_140-2#Level_2">article</a>): <blockquote>Security Level 2 improves upon the physical security mechanisms of a Security Level 1 cryptographic module by requiring features that show evidence of tampering, including tamper-evident coatings or seals that must be broken to attain physical access to the plaintext cryptographic keys and critical security parameters (CSPs) within the module, or pick-resistant locks on covers or doors to protect against unauthorized physical access.</blockquote>Thus you can't get the key without leaving traces.  BTW: I'm sure the messages in "Mission: Impossible" are FIPS140-2 Level 5 certified ... "This tape will self-destruct in five seconds" <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/wink.png" alt=";-)" style="display: inline; vertical-align: bottom;" class="emoticon" /><br />
<br />
The T10000B is the first tape-drive with this level of certification. If you are interested in this matter, the certification of the T10000B is available <a onclick="_gaq.push(['_trackPageview', '/extlink/csrc.nist.gov/groups/STM/cmvp/documents/140-1/140crt/140crt1156.pdf']);"  href="http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140crt/140crt1156.pdf">the nist.gov</a> website. The FIPS140-12 document itself is available <a onclick="_gaq.push(['_trackPageview', '/extlink/csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf']);"  href="http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf">for download</a> at NIST, too. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/FgOI3rcqDDA" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 20 Aug 2009 21:12:23 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5873-guid.html</guid>
    <category>storage</category>
<category>sun</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5873-FIPS-140-2-Sec-Level-2-for-Sun-Tape-drive.html</feedburner:origLink></item>
<item>
    <title>Secure Deletion with ZFS</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/KJgyCXRVqzs/5793-Secure-Deletion-with-ZFS.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5793-Secure-Deletion-with-ZFS.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5793</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5793</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    A reader that wants to be anonymous (thus he use such a pseudo in his comments) asked an interesting question: How do you do secure deletion in ZFS? The standard mechanism to it, is to overwrite data with zeros, ones or a data pattern to ensure that the data is deleted as normal delete would only delete the metadata and not the data itself. This is a little bit hard with ZFS. Why? ZFS is a copy-on-write filesystem, thus the zeros are written somewhere else, as active data is never overwritten by ZFS.  There are hacks to solve this problems: For example overwriting all sectors on the free list. Or you can implement code to overwrite the data directly in a kind of secure delete. But from my point of view this wouldn´t really help.<br />
 <br /><a href="http://www.c0t0d0s0.org/archives/5793-Secure-Deletion-with-ZFS.html#extended">Continue reading "Secure Deletion with ZFS"</a>
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/KJgyCXRVqzs" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 27 Jul 2009 13:12:43 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5793-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5793-Secure-Deletion-with-ZFS.html</feedburner:origLink></item>
<item>
    <title>Webseminar: "Solaris Security"</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/WMhcdvxgFgc/5782-Webseminar-Solaris-Security.html</link>
            <category>German</category>
            <category>Security</category>
            <category>Solaris</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5782-Webseminar-Solaris-Security.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5782</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5782</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Ich hatte ja schon vor einigen Tagen angekündigt, das es bald wieder ein neues Webseminar von mir geben wird: Ich werde in diesem Seminar auf die ganzen Sicherheitsfeatures in Solaris eingehen. Also wie gehe ich mit Least Privileges um, was hat es mit den signed Binaries auf sich, was bedeutet eigentlich EAL und Common Criteria, wie können mir die Trusted Extensions weiterhelfen, was ist die Solaris Fingerprint Database und vieles mehr. Stattfinden wird dieses Webseminar Seminar am 30 September 2009 von 14:00 bis 15:00 Uhr.  Für dieses kann man sich nunmehr auch anmelden. Das Anmeldeformular findet Ihr <a onclick="_gaq.push(['_trackPageview', '/extlink/dct.sun.com/dct/forms/reg_de_2307_986_0.jsp']);"  href="https://dct.sun.com/dct/forms/reg_de_2307_986_0.jsp">hier</a>.<br />
<br />
Bei dieser Gelegenheit möchte ich gleich noch auf drei weitere Webseminare hinweisen: Am 26. August wird Volker Wetter (Technical Architect Systems Pratice) zum Thema "10 Gründe, Ihre Applikation auf Solaris zu betreiben" sprechen. Für den 16. September ist dann ein Vortrag zum Thema "Sun Unified Storage in der Praxis" geplant. Dieser wird von  Karlheinz Vogel, seines Zeichens Senior Storage Consultant vorgetragen. Der Holodoc, sorry ... Dr. Stefan Schneider, Chief Technologist, wird sich dann  am 22. September mit dem Thema "Start smart. Scale hard! Warum Web-Startups mit Ihrer IT skalieren müssen" befassen. Weitere Informationen findet Ihr dazu auf der Webseite <a onclick="_gaq.push(['_trackPageview', '/extlink/de.sun.com/sunnews/webinar/']);"  href="http://de.sun.com/sunnews/webinar/">der deutschen Sun Webseminare.</a><br />
<br />
PS: Entschuldigt bitte den Text bei der Beschreibung meines Seminars. Is vom Produktmarketing. Der Vortrag ist marketingfrei <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/WMhcdvxgFgc" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 23 Jul 2009 17:18:23 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5782-guid.html</guid>
    <category>solaris</category>
<category>storage</category>
<category>sun</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5782-Webseminar-Solaris-Security.html</feedburner:origLink></item>
<item>
    <title>The Register about ZFS deduplication</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/DU-lQrtOdRA/5737-The-Register-about-ZFS-deduplication.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5737-The-Register-about-ZFS-deduplication.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5737</wfw:comment>

    <slash:comments>7</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5737</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Even the Register reports about <a onclick="_gaq.push(['_trackPageview', '/extlink/www.theregister.co.uk/2009/07/13/zfs_deduplication/']);"  href="http://www.theregister.co.uk/2009/07/13/zfs_deduplication/">Deduplication in ZFS</a>. I´m asking myself, if the people at the Register read my blog, as i´ve talked about that a few days ago.<br />
<br />
 Fun aside: Synchronous Dedupe is the only sensible way to do dedupe data as you would need to provide the storage for undeduped  data otherwise until the system gets to the point where the data gets deduplicated. Dependent on the frequency of dedupe runs, this could be a vast amount of storage. On the other side, synchronous dedupe is dependent of a fast mechanism to detect duplicates. The checksumming feature of ZFS looks like a good way to do this, as it capable to use various hashing algorithms. When the probability of collision is less than the probability of reading wrong data from disks it should suffice just to check the checksums instead of checking the complete block. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/DU-lQrtOdRA" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 13 Jul 2009 14:34:43 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5737-guid.html</guid>
    <category>storage</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5737-The-Register-about-ZFS-deduplication.html</feedburner:origLink></item>
<item>
    <title>Kompetenz in Computersicherheit</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/ohHRrPi_Dtc/5706-Kompetenz-in-Computersicherheit.html</link>
            <category>German</category>
            <category>policy of ...</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5706-Kompetenz-in-Computersicherheit.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5706</wfw:comment>

    <slash:comments>8</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5706</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Soviel zum Thema Kompetenz zum Thema Computersicherheit: Herr Schünemann <a onclick="_gaq.push(['_trackPageview', '/extlink/unintendedpurpose.wordpress.com/2009/07/01/klasse-wtf-das-sieht-aus-wie-ein-fake-ist-aber-real-und-mein-fundstuck-des-monats-fail-schuenemann/']);"  href="http://unintendedpurpose.wordpress.com/2009/07/01/klasse-wtf-das-sieht-aus-wie-ein-fake-ist-aber-real-und-mein-fundstuck-des-monats-fail-schuenemann/">sitzt vor einem Rechner des LKA</a>. Achtet mal auf den Monitor. Ich vermute das ist ein DemoPC, aber trotzdem: Sowas macht man nicht ... 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/ohHRrPi_Dtc" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 02 Jul 2009 13:19:13 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5706-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5706-Kompetenz-in-Computersicherheit.html</feedburner:origLink></item>
<item>
    <title>A sniffer for wireless keyboards</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/0ZVWhKQp9ds/5663-A-sniffer-for-wireless-keyboards.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5663-A-sniffer-for-wireless-keyboards.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5663</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5663</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    You should opt for a new keyboard, when you use certain wireless keyboards. Thorsten Schroeder &amp; Max Moser of Dreamlab Technologies published the software and the hardware to enable someone to intercept the keystrokes. You can read more about it at their <a onclick="_gaq.push(['_trackPageview', '/extlink/www.remote-exploit.org/Keykeriki.html']);"  href="http://www.remote-exploit.org/Keykeriki.html">webpage for their Keykeriki project</a>. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/0ZVWhKQp9ds" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 17 Jun 2009 16:56:32 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5663-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5663-A-sniffer-for-wireless-keyboards.html</feedburner:origLink></item>
<item>
    <title>Updated Security Deep Dive</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/F0t4HJl7JJA/5660-Updated-Security-Deep-Dive.html</link>
            <category>English</category>
            <category>Security</category>
            <category>Solaris</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5660-Updated-Security-Deep-Dive.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5660</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5660</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Glenn Brunette updated his <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.sun.com/gbrunett/entry/new_solaris_10_security_deep2']);"  href="http://blogs.sun.com/gbrunett/entry/new_solaris_10_security_deep2">Solaris 10 Security Deep Dive</a> presentation to represent the changes in Solaris 10 U7.  
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/F0t4HJl7JJA" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 16 Jun 2009 22:29:56 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5660-guid.html</guid>
    <category>solaris</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5660-Updated-Security-Deep-Dive.html</feedburner:origLink></item>
<item>
    <title>Insights to HTTPS</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/lnfgJ2IgXN8/5641-Insights-to-HTTPS.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5641-Insights-to-HTTPS.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5641</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5641</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    We all take the function of SSL and TLS as granted for our secure communication needs while surfing in the web or for encrypting the access to our mailboxes. But before we can start to communicate, a lot of stuff happens: Jeff Moser wrote an excellent article about the <a onclick="_gaq.push(['_trackPageview', '/extlink/www.moserware.com/2009/06/first-few-milliseconds-of-https.html']);"  href="http://www.moserware.com/2009/06/first-few-milliseconds-of-https.html">first few seconds in the life of a HTTPS connection.</a>  
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/lnfgJ2IgXN8" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 11 Jun 2009 21:14:15 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5641-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5641-Insights-to-HTTPS.html</feedburner:origLink></item>
<item>
    <title>The nature of security bugs</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/srKq_I7JaIo/5471-The-nature-of-security-bugs.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5471-The-nature-of-security-bugs.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5471</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5471</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Hits the nail on its head:<blockquote>Security fixes are different from every other kind of fix. As every good troubleshooter knows, when problems occur something almost invariably has changed. For most bugs it is something like load, configuration and so on which can be undone.<br />
With security bugs it is knowledge that has changed and a security weakness can't be unlearned by the world at large.</blockquote><br />
Peter Harvey wrote this <a onclick="_gaq.push(['_trackPageview', '/extlink/blogs.sun.com/peteh/entry/why_security_bugs_are_different']);"  href="http://blogs.sun.com/peteh/entry/why_security_bugs_are_different">in his blog and</a> i think he is correct with his insight. But i would add a hybrid group. There are security bugs similar to the normal fixes. Introduced by normal bugs ... or lazy checking. And then there are security weaknesses inherent in a protocol or idea. Those can´t be unlearned at all from the world. You can´t even fix it when the protocol has a huge acceptance in the network. Just think about the long standing search for a more SPAM resistant SMTP ... or the recent discussions about weaknesses in BGP. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/srKq_I7JaIo" height="1" width="1"/>]]></content:encoded>

    <pubDate>Thu, 16 Apr 2009 22:57:34 +0200</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5471-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5471-The-nature-of-security-bugs.html</feedburner:origLink></item>
<item>
    <title>Wirklich peinlich</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/KXquPFcrlQk/5424-Wirklich-peinlich.html</link>
            <category>German</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5424-Wirklich-peinlich.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5424</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5424</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Da rennt die Polizei seit geraumer Zeit einer unbekannten weiblichen Person hinterher, die Spuren an Dutzenden von Tatorten hinterlassen haben sollen, beispielsweise auch an jenem des Polizistinnenmords von Heilbronn. Ich hatte mich ja auch schon gewundert, wie umtriebig diese Dame ist, die mittlerweile von der Presse schon "Phantom" genannt wurde.<br />
<br />
Der Stern berichtet nun, das <a onclick="_gaq.push(['_trackPageview', '/extlink/www.stern.de/panorama/:Polizistenmord-Heilbronn-R%E4tsel-Phantom/659006.html']);"  href="http://www.stern.de/panorama/:Polizistenmord-Heilbronn-R%E4tsel-Phantom/659006.html">man unter Umständen lediglich die DNA einer Verpackerin von Wattestäbchen zur Aufnahme von solchen Beweisen gefunden hat, die diese unvorsichtigerweise beim Einpacken mit eigenen Zellen kontaminiert hat</a>. Das ist irgendwie ... wirklich peinlich. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/KXquPFcrlQk" height="1" width="1"/>]]></content:encoded>

    <pubDate>Wed, 25 Mar 2009 19:46:26 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5424-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5424-Wirklich-peinlich.html</feedburner:origLink></item>
<item>
    <title>Botnets ... based on routers - revisited</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/m9DVphms_aM/5413-Botnets-...-based-on-routers-revisited.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5413-Botnets-...-based-on-routers-revisited.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5413</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5413</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    While waiting for my tea water to boiling, i had an idea: Perhaps it´s much easier to <a href="http://www.c0t0d0s0.org/archives/5411-Botnets-...-based-on-routers.html">hack a router to a botnet drone</a> than i initially thought. I think it´s consensus, that Windows based PC are still easily infectable with bots. But the PC are under steady control by their users. As tight as the firewalls of these routers are to the outside, as open they are to the inside. I think it would be nice idea, to target the Windows PC at first, infect the router from there (it´s easy to find the router ... it´s the default router). Perhaps by an exploit for the remote administration software or just by router passwords stored in the browser password chain. After infecting the router, the bot could remove itself from the Windows PC without leaving traces. An bot detection tool can´t find something on the PC and it doesn´t check the router for an infection. Well ... you can think about Trusted Execution or TPMs what you want ... but there are valid use cases outside DRM.<br />
<br />
It´s a little bit like tonsillectomy by opening the chest, but sometimes it´s easier this way ... especially when the patient don´t want to open the mouth <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/m9DVphms_aM" height="1" width="1"/>]]></content:encoded>

    <pubDate>Tue, 24 Mar 2009 09:15:58 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5413-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5413-Botnets-...-based-on-routers-revisited.html</feedburner:origLink></item>
<item>
    <title>Botnets ... based on routers</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/1lgAmSZnlSE/5411-Botnets-...-based-on-routers.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5411-Botnets-...-based-on-routers.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5411</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5411</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    With a sharp tongue, you could state: Microsoft already proofed that cloud computing is a economic success. The large botnets in the Internet are nothing else than clouds, even with SaaS (no, not software as a service, spam/scam as a service). And you can make really a money by owning a botnet. Well ... I hope that the discovery of DroneBL doesn´t lead to a much larger wave of BotNets.<br />
<br />
The worst managed computer system in the common household is often not the Windows PC .... it´s the small Linux computer that got ubiquitous since DSL or cable internet is something normal. Most people configure them once, put them somewhere in a closet and forget them. So it was just a matter of time before someone would have created a botnet consisting out of this small routers. DroneBL writes about <a onclick="_gaq.push(['_trackPageview', '/extlink/www.dronebl.org/blog/8']);"  href="http://www.dronebl.org/blog/8">such a botnet</a>.<br />
<br />
When you really think about it: These small routers are a perfect target. They run 24h/7days a week. Most people don´t really look at them, so they can´t detect strange traffic patterns by looking at the blinkenlights. Furthermore the once you have an exploit for a certain type of router, it´s highly probable that you can exploit a vast amount of systems. Depending on the type of the router, there is a large population of identical system. Just a thought game: Let´s assume, you find an exploit for a brand of routers distributed by almost all ISP in a country to their end customers. This would be a hell of a botnet. Millions of members <img src="http://www.c0t0d0s0.org/templates/default/img/emoticons/wink.png" alt=";-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> Obviously the first action of such an exploit would be the deactivation of online router software update and the redirection of any request to the support website. It would be really hard to get rid of this bot.<br />
<br />
I hope the developers of the OS of such small router boxes are aware of their responsibility ... an error could be an really nasty home run for the dark side.<br />
 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/1lgAmSZnlSE" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 23 Mar 2009 20:26:54 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5411-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5411-Botnets-...-based-on-routers.html</feedburner:origLink></item>
<item>
    <title>Deniable </title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/-5zsCWC92Xs/5336-Deniable.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5336-Deniable.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5336</wfw:comment>

    <slash:comments>8</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5336</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    I just thought about an interesting for the mechanism explained in <a href="http://www.c0t0d0s0.org/archives/5335-Proof-of-concept-hack-for-encrypted-direct-messages-on-Twitter.html">"Proof of concept hack for encrypted direct messages on Twitter</a> - you could deny that you are the intended receiver of the message. Just post the encrypted stuff as a public tweet. The recipient just have to read the public timeline and just reads all messages, gathers all crypted tweets and tries to decrypt them. Messages for other people are unencryptable for you, as you don´t have the correct secret key, but the messages for you are encryptable, thus you know, that the messages are for you.<br />
<br />
BTW: You could use blog comments as well to transmit such messages. Just distribute a line per blog comment on a vast amount of messages. They have just a single point in common .... the pages with the comments are part of the first few hundred hits in Google blog search. The recipient knows the correct query (a shared secret for example  as the google query "What to do with coronary insufficiency?")and is able to gather them, reassembles them and tries to decode it.<br />
<br />
The whole mechanism described in this article isn´t new at all. It is the same idea used for the strange radio stations sending <a onclick="_gaq.push(['_trackPageview', '/extlink/en.wikipedia.org/wiki/Numbers_station']);"  href="http://en.wikipedia.org/wiki/Numbers_station">just rows of numbers.</a><br />
<br />
Update: The actual code of the proof-of-concept doesn´t strip of the key-ids. Before using this code, you have to add <code>--throw-keyids</code> to <code>gpgopts($opts)</code>. But i have to reiterate about this: The code was meant to test encryption and reassembly/decryption ... it´s not meant as actual production code. 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/-5zsCWC92Xs" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 23 Feb 2009 13:41:59 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5336-guid.html</guid>
    <category>encryption</category>
<category>gnu privacy guard</category>
<category>hack</category>
<category>perl</category>
<category>security</category>
<category>twitter</category>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5336-Deniable.html</feedburner:origLink></item>
<item>
    <title>Brute force in cryptography - literally</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/XxPhsnSvD4M/5276-Brute-force-in-cryptography-literally.html</link>
            <category>English</category>
            <category>Security</category>
    
    <comments>http://www.c0t0d0s0.org/archives/5276-Brute-force-in-cryptography-literally.html#comments</comments>
    <wfw:comment>http://www.c0t0d0s0.org/wfwcomment.php?cid=5276</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.c0t0d0s0.org/rss.php?version=2.0&amp;type=comments&amp;cid=5276</wfw:commentRss>
    

    <author>nospam@example.com (Joerg Moellenkamp)</author>
    <content:encoded><![CDATA[
    Most of the times brute-force algorithms are much more effective than even the most sophisticated crypto analysis:<br />
<br />
<center><a onclick="_gaq.push(['_trackPageview', '/extlink/xkcd.com/538/']);"  href="http://xkcd.com/538/"><img border=0 src="http://imgs.xkcd.com/comics/security.png"></a><br />
<small>(found at xkcd.com)</small></center> 
    <img src="http://feeds.feedburner.com/~r/C0t0d0s0org-Security/~4/XxPhsnSvD4M" height="1" width="1"/>]]></content:encoded>

    <pubDate>Mon, 02 Feb 2009 11:21:58 +0100</pubDate>
    <guid isPermaLink="false">http://www.c0t0d0s0.org/archives/5276-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.5/</creativeCommons:license>
<feedburner:origLink>http://www.c0t0d0s0.org/archives/5276-Brute-force-in-cryptography-literally.html</feedburner:origLink></item>
<item>
    <title>Yet another security theater</title>
    <link>http://feedproxy.google.com/~r/C0t0d0s0org-Security/~3/DteBE_cbz1I/4553-Yet-another-security-theater.html</link>
            <category>English</category>
            <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="_gaq.push(['_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="_gaq.push(['_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/DteBE_cbz1I" 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>

</channel>
</rss>

