<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet href="/templates/default/atom.css" type="text/css" ?>

<feed 
   xmlns="http://www.w3.org/2005/Atom"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/">
    <link href="http://blog.florianlaws.de/feeds/atom.xml" rel="self" title="flawed concepts" type="application/atom+xml" />
    <link href="http://blog.florianlaws.de/"                        rel="alternate"    title="flawed concepts" type="text/html" />
    <link href="http://blog.florianlaws.de/rss.php?version=2.0"     rel="alternate"    title="flawed concepts" type="application/rss+xml" />
    <title type="html">flawed concepts</title>
    <subtitle type="html"></subtitle>
    <icon>http://blog.florianlaws.de/templates/default/img/s9y_banner_small.png</icon>
    <id>http://blog.florianlaws.de/</id>
    <updated>2010-03-28T23:25:19Z</updated>
    <generator uri="http://www.s9y.org/" version="1.2-beta2">Serendipity 1.2-beta2 - http://www.s9y.org/</generator>
    <dc:language>de</dc:language>

    <entry>
        <link href="http://blog.florianlaws.de/archives/209-Security-Advice-Is-Wrong.html" rel="alternate" title="Security Advice Is Wrong" />
        <author>
            <name>florian</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2010-03-28T23:25:19Z</published>
        <updated>2010-03-28T23:25:19Z</updated>
        <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=atom1.0&amp;type=comments&amp;cid=209</wfw:commentRss>
    
            <category scheme="http://blog.florianlaws.de/categories/9-english" label="english" term="english" />
            <category scheme="http://blog.florianlaws.de/categories/8-german" label="german" term="german" />
    
        <id>http://blog.florianlaws.de/archives/209-guid.html</id>
        <title type="html">Security Advice Is Wrong</title>
        <content type="xhtml" xml:base="http://blog.florianlaws.de/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Cormac Herley, Microsoft Research: "So Long, And No Thanks for the Externalities: The Rational Rejection of Security Advice by Users" <a href="http://research.microsoft.com/en-us/um/people/cormac/papers/2009/solongandnothanks.pdf">(PDF)</a><br />
<br />
via <a href="http://glinden.blogspot.com/2010/03/security-advice-is-wrong.html">Greg Linden</a> 
            </div>
        </content>
        <dc:subject>security</dc:subject>
<dc:subject>security</dc:subject>

    </entry>
    <entry>
        <link href="http://blog.florianlaws.de/archives/208-IT-Security-meets-Natural-Language-Processing.html" rel="alternate" title="IT Security meets Natural Language Processing" />
        <author>
            <name>florian</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2010-03-17T21:24:42Z</published>
        <updated>2010-03-17T21:24:42Z</updated>
        <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=atom1.0&amp;type=comments&amp;cid=208</wfw:commentRss>
    
            <category scheme="http://blog.florianlaws.de/categories/9-english" label="english" term="english" />
    
        <id>http://blog.florianlaws.de/archives/208-guid.html</id>
        <title type="html">IT Security meets Natural Language Processing</title>
        <content type="xhtml" xml:base="http://blog.florianlaws.de/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                <a href="http://lingpipe-blog.com/2010/03/09/language-model-generated-injection-attacks-cooldisturbing-lingpipe-application/">Language Model Generated Injection Attacks: Cool/Disturbing LingPipe Application</a><br />
<br />
read: Shellcode that looks like English.<br />
<br />
Amazing. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.florianlaws.de/archives/206-badblocklocate-Find-LVM2-logical-volume-containing-a-block.html" rel="alternate" title="badblocklocate: Find LVM2 logical volume containing a block" />
        <author>
            <name>florian</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2009-06-21T17:16:09Z</published>
        <updated>2009-06-21T17:16:09Z</updated>
        <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=atom1.0&amp;type=comments&amp;cid=206</wfw:commentRss>
    
            <category scheme="http://blog.florianlaws.de/categories/10-computing" label="computing" term="computing" />
            <category scheme="http://blog.florianlaws.de/categories/9-english" label="english" term="english" />
    
        <id>http://blog.florianlaws.de/archives/206-guid.html</id>
        <title type="html">badblocklocate: Find LVM2 logical volume containing a block</title>
        <content type="xhtml" xml:base="http://blog.florianlaws.de/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                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.<br />
<br />
The excellent <a href="http://smartmontools.sourceforge.net/badblockhowto.html">Bad block HOWTO for smartmontools</a> 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. <br />
<br />
Therefore, I have written a small script that performs the calculations and determines the LVM2 volume that contains a given block number: <a href="http://www.florianlaws.de/software/badblocklocate.py">badblocklocate.py</a>.<br />
<br />
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.<br />
<br />
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.  
            </div>
        </content>
        
    </entry>

</feed>