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

<rss version="2.0" 
   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/"
   >
<channel>
    <title>flawed concepts - english</title>
    <link>http://blog.florianlaws.de/</link>
    <description></description>
    <dc:language>de</dc:language>
    <generator>Serendipity 1.2-beta2 - http://www.s9y.org/</generator>
    <pubDate>Sun, 28 Mar 2010 23:25:19 GMT</pubDate>

    <image>
        <url>http://blog.florianlaws.de/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: flawed concepts - english - </title>
        <link>http://blog.florianlaws.de/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Security Advice Is Wrong</title>
    <link>http://blog.florianlaws.de/archives/209-Security-Advice-Is-Wrong.html</link>
            <category>english</category>
            <category>german</category>
    
    <comments>http://blog.florianlaws.de/archives/209-Security-Advice-Is-Wrong.html#comments</comments>
    <wfw:comment>http://blog.florianlaws.de/wfwcomment.php?cid=209</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://blog.florianlaws.de/rss.php?version=2.0&amp;type=comments&amp;cid=209</wfw:commentRss>
    

    <author>nospam@example.com (florian)</author>
    <content:encoded>
    Cormac Herley, Microsoft Research: &quot;So Long, And No Thanks for the Externalities: The Rational Rejection of Security Advice by Users&quot; &lt;a href=&quot;http://research.microsoft.com/en-us/um/people/cormac/papers/2009/solongandnothanks.pdf&quot;&gt;(PDF)&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
via &lt;a href=&quot;http://glinden.blogspot.com/2010/03/security-advice-is-wrong.html&quot;&gt;Greg Linden&lt;/a&gt; 
    </content:encoded>

    <pubDate>Mon, 29 Mar 2010 01:25:19 +0200</pubDate>
    <guid isPermaLink="false">http://blog.florianlaws.de/archives/209-guid.html</guid>
    <category>security</category>
<category>security</category>

</item>
<item>
    <title>IT Security meets Natural Language Processing</title>
    <link>http://blog.florianlaws.de/archives/208-IT-Security-meets-Natural-Language-Processing.html</link>
            <category>english</category>
    
    <comments>http://blog.florianlaws.de/archives/208-IT-Security-meets-Natural-Language-Processing.html#comments</comments>
    <wfw:comment>http://blog.florianlaws.de/wfwcomment.php?cid=208</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.florianlaws.de/rss.php?version=2.0&amp;type=comments&amp;cid=208</wfw:commentRss>
    

    <author>nospam@example.com (florian)</author>
    <content:encoded>
    &lt;a href=&quot;http://lingpipe-blog.com/2010/03/09/language-model-generated-injection-attacks-cooldisturbing-lingpipe-application/&quot;&gt;Language Model Generated Injection Attacks: Cool/Disturbing LingPipe Application&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
read: Shellcode that looks like English.&lt;br /&gt;
&lt;br /&gt;
Amazing. 
    </content:encoded>

    <pubDate>Wed, 17 Mar 2010 22:24:42 +0100</pubDate>
    <guid isPermaLink="false">http://blog.florianlaws.de/archives/208-guid.html</guid>
    
</item>
<item>
    <title>badblocklocate: Find LVM2 logical volume containing a block</title>
    <link>http://blog.florianlaws.de/archives/206-badblocklocate-Find-LVM2-logical-volume-containing-a-block.html</link>
            <category>computing</category>
            <category>english</category>
    
    <comments>http://blog.florianlaws.de/archives/206-badblocklocate-Find-LVM2-logical-volume-containing-a-block.html#comments</comments>
    <wfw:comment>http://blog.florianlaws.de/wfwcomment.php?cid=206</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.florianlaws.de/rss.php?version=2.0&amp;type=comments&amp;cid=206</wfw:commentRss>
    

    <author>nospam@example.com (florian)</author>
    <content:encoded>
    When SMART tells you about possibly defective hard disk blocks, you might want to know what volumes are affected so you can perform extra precautions or rewrite the data to the the disk to reallocate the affected blocks.&lt;br /&gt;
&lt;br /&gt;
The excellent &lt;a href=&quot;http://smartmontools.sourceforge.net/badblockhowto.html&quot;&gt;Bad block HOWTO for smartmontools&lt;/a&gt; tells you how to do this, but is too easy to get confused by all the different block numbers, sizes and offsets you have to calculate. &lt;br /&gt;
&lt;br /&gt;
Therefore, I have written a small script that performs the calculations and determines the LVM2 volume that contains a given block number: &lt;a href=&quot;http://www.florianlaws.de/software/badblocklocate.py&quot;&gt;badblocklocate.py&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Can determine LVM2 logical volume names from block numbers given on the command line, or can call smartctl to automatically determine defective blocks. Please see the comments at the top of the file for usage information.&lt;br /&gt;
&lt;br /&gt;
For now, it works for LVM2 logical volumes only (though classical partitions can be determined through the error message.) If time permits, i might extend it that it also determines which file contains the defective blocks.  
    </content:encoded>

    <pubDate>Sun, 21 Jun 2009 19:16:09 +0200</pubDate>
    <guid isPermaLink="false">http://blog.florianlaws.de/archives/206-guid.html</guid>
    
</item>

</channel>
</rss>