<?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>NickNack's personal blog - Linux</title>
    <link>http://cryingwolf.net/</link>
    <description>Thoughts From the back of my brain</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.3.1 - http://www.s9y.org/</generator>
    <pubDate>Tue, 02 Oct 2007 13:40:43 GMT</pubDate>

    <image>
        <url>http://cryingwolf.net/templates/default/cryingwolf.jpg</url>
        <title>RSS: NickNack's personal blog - Linux - Thoughts From the back of my brain</title>
        <link>http://cryingwolf.net/</link>
        <width>100</width>
        <height>80</height>
    </image>

<item>
    <title>Fight Trackback Spam with apache mod_env</title>
    <link>http://cryingwolf.net/archives/164-Fight-Trackback-Spam-with-apache-mod_env.html</link>
            <category>Linux</category>
            <category>Net Stuffs</category>
    
    <comments>http://cryingwolf.net/archives/164-Fight-Trackback-Spam-with-apache-mod_env.html#comments</comments>
    <wfw:comment>http://cryingwolf.net/wfwcomment.php?cid=164</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cryingwolf.net/rss.php?version=2.0&amp;type=comments&amp;cid=164</wfw:commentRss>
    

    <author>nospam@example.com (NickNack)</author>
    <content:encoded>
    I noticed a lot of bots trying to abuse my trackback,&lt;br /&gt;
by checking in site&#039;s log :
&lt;br /&gt;&lt;br /&gt;
&lt;div class=&quot;code&quot;&gt;
POST /comment.php?type=trackback&amp;amp;entry_id=20 &lt;br /&gt;
HTTP/1.0 200 87 - TrackBack/1.02
&lt;/div&gt;
&lt;br /&gt;&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://cryingwolf.net/archives/164-Fight-Trackback-Spam-with-apache-mod_env.html#extended&quot;&gt;Continue reading &quot;Fight Trackback Spam with apache mod_env&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 13 Aug 2007 22:28:13 +0700</pubDate>
    <guid isPermaLink="false">http://cryingwolf.net/archives/164-guid.html</guid>
    
</item>
<item>
    <title>Spamdyke, A drop-in connection-time spam filter for qmail</title>
    <link>http://cryingwolf.net/archives/161-Spamdyke,-A-drop-in-connection-time-spam-filter-for-qmail.html</link>
            <category>Linux</category>
    
    <comments>http://cryingwolf.net/archives/161-Spamdyke,-A-drop-in-connection-time-spam-filter-for-qmail.html#comments</comments>
    <wfw:comment>http://cryingwolf.net/wfwcomment.php?cid=161</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cryingwolf.net/rss.php?version=2.0&amp;type=comments&amp;cid=161</wfw:commentRss>
    

    <author>nospam@example.com (NickNack)</author>
    <content:encoded>
    &lt;a href=&quot;http://www.spamdyke.org/&quot; &gt;Spamdyke&lt;/a&gt; is a filter for monitoring and intercepting SMTP connections &lt;br /&gt;between a remote host and a qmail server.
&lt;br /&gt;&lt;br /&gt;
When a connection is established from a spam source &lt;br /&gt;
(as determined by the active filters), spamdyke will reject the email &lt;br /&gt;
qmail never sees it.
&lt;br /&gt;
&lt;br /&gt;
Beyond filtering, spamdyke offers a number of other features:&lt;br /&gt;
&amp;bull;   spamdyke supports SMTP AUTH and will even provide SMTP AUTH to an unpatched &lt;br /&gt;
            qmail server.&lt;br /&gt;&lt;br /&gt;
&amp;bull;   spamdyke supports TLS and will even provide TLS to an unpatched qmail server.&lt;br /&gt;&lt;br /&gt;
&amp;bull;   spamdyke provides much better, much more complete logging than qmail, &lt;br /&gt;
            using syslogd.&lt;br /&gt;&lt;br /&gt;
&amp;bull;   spamdyke can log all SMTP traffic to aid troubleshooting. &lt;br /&gt;
&lt;br /&gt;&lt;br /&gt;
So folks, this might worth to try &lt;img src=&quot;&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;
 
    </content:encoded>

    <pubDate>Sat, 11 Aug 2007 17:37:09 +0700</pubDate>
    <guid isPermaLink="false">http://cryingwolf.net/archives/161-guid.html</guid>
    
</item>
<item>
    <title>Defeating SSH Brute Force Attack</title>
    <link>http://cryingwolf.net/archives/159-Defeating-SSH-Brute-Force-Attack.html</link>
            <category>Debian</category>
            <category>Linux</category>
    
    <comments>http://cryingwolf.net/archives/159-Defeating-SSH-Brute-Force-Attack.html#comments</comments>
    <wfw:comment>http://cryingwolf.net/wfwcomment.php?cid=159</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://cryingwolf.net/rss.php?version=2.0&amp;type=comments&amp;cid=159</wfw:commentRss>
    

    <author>nospam@example.com (NickNack)</author>
    <content:encoded>
    I got hundreds of ssh brute force login attack on my /var/log/auth.log everyday..
&lt;br /&gt;
This solutions is simple, yet effective..&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;code&quot;&gt;
apt-get install denyhost
&lt;/div&gt;
&lt;br /&gt;
edit /etc/denyhost.conf to suite your environment,&lt;br /&gt;
then have a great life &lt;img src=&quot;&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;&lt;br /&gt;

 
    </content:encoded>

    <pubDate>Mon, 09 Jul 2007 13:32:08 +0700</pubDate>
    <guid isPermaLink="false">http://cryingwolf.net/archives/159-guid.html</guid>
    
</item>
<item>
    <title>hwclock and rtc device driver</title>
    <link>http://cryingwolf.net/archives/137-hwclock-and-rtc-device-driver.html</link>
            <category>Linux</category>
    
    <comments>http://cryingwolf.net/archives/137-hwclock-and-rtc-device-driver.html#comments</comments>
    <wfw:comment>http://cryingwolf.net/wfwcomment.php?cid=137</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cryingwolf.net/rss.php?version=2.0&amp;type=comments&amp;cid=137</wfw:commentRss>
    

    <author>nospam@example.com (NickNack)</author>
    <content:encoded>
    hwclock seems to behave weird on newer kernels..&lt;br /&gt;
&lt;pre&gt;
zebulon:/etc# hwclock  --systohc&lt;br /&gt;
select() to /dev/rtc to wait for clock tick timed out
&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://cryingwolf.net/archives/137-hwclock-and-rtc-device-driver.html#extended&quot;&gt;Continue reading &quot;hwclock and rtc device driver&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 02 Nov 2006 07:43:03 +0700</pubDate>
    <guid isPermaLink="false">http://cryingwolf.net/archives/137-guid.html</guid>
    
</item>
<item>
    <title>Phpmyadmin Woe</title>
    <link>http://cryingwolf.net/archives/104-Phpmyadmin-Woe.html</link>
            <category>Debian</category>
            <category>IT / Tech</category>
            <category>Linux</category>
    
    <comments>http://cryingwolf.net/archives/104-Phpmyadmin-Woe.html#comments</comments>
    <wfw:comment>http://cryingwolf.net/wfwcomment.php?cid=104</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cryingwolf.net/rss.php?version=2.0&amp;type=comments&amp;cid=104</wfw:commentRss>
    

    <author>nospam@example.com (NickNack)</author>
    <content:encoded>
    &lt;strong&gt;&quot;Client does not support authentication protocol requested by server; &lt;br /&gt;
consider upgrading MySQL client&quot;&lt;/strong&gt;&lt;br /&gt;
Arrrgh !&lt;br /&gt;
&lt;br /&gt;
Quick look at phpmyfaq gimme the solutions, tho&#039;...&lt;br /&gt;
&lt;br /&gt;
My mysql server&#039;s version is 5.0.18-Debian_8, My PHP version was 4, and I use Apache2, &lt;br /&gt;
they said the mysql lib of php4 is too old for the server. &lt;br /&gt;
so I upgrade php , its mysql lib, and php5 module for apache2 :&lt;br /&gt;
&lt;pre&gt;apt-get install php5 php5-mysql libapache2-mod-php5&lt;/pre&gt;&lt;br /&gt;
Restart apache, and Voila ! phpmyadmin works again ! &lt;img src=&quot;&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;
&lt;br /&gt;

 
    </content:encoded>

    <pubDate>Tue, 07 Mar 2006 15:58:52 +0700</pubDate>
    <guid isPermaLink="false">http://cryingwolf.net/archives/104-guid.html</guid>
    
</item>
<item>
    <title>DEBIAN APT : Debian KeyRing</title>
    <link>http://cryingwolf.net/archives/25-DEBIAN-APT-Debian-KeyRing.html</link>
            <category>Debian</category>
            <category>Linux</category>
    
    <comments>http://cryingwolf.net/archives/25-DEBIAN-APT-Debian-KeyRing.html#comments</comments>
    <wfw:comment>http://cryingwolf.net/wfwcomment.php?cid=25</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://cryingwolf.net/rss.php?version=2.0&amp;type=comments&amp;cid=25</wfw:commentRss>
    

    <author>nospam@example.com (NickNack)</author>
    <content:encoded>
    &lt;div class=&quot;code&quot;&gt;W: GPG error: http://debian.3wsi.net testing/non-US &lt;br /&gt;Release: The following signatures couldn&#039;t be verified&lt;br /&gt; because the public key is not available: NO_PUBKEY KEY_ID&lt;/div&gt; &lt;br /&gt;&lt;a href=&quot;http://cryingwolf.net/archives/25-DEBIAN-APT-Debian-KeyRing.html#extended&quot;&gt;Continue reading &quot;DEBIAN APT : Debian KeyRing&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 13 Feb 2006 20:05:00 +0700</pubDate>
    <guid isPermaLink="false">http://cryingwolf.net/archives/25-guid.html</guid>
    
</item>
<item>
    <title>Debian packages for Canon Pixus iP3100 / ip4100 / ip8600 (and Pixma iP1000 / iP1500)</title>
    <link>http://cryingwolf.net/archives/86-Debian-packages-for-Canon-Pixus-iP3100-ip4100-ip8600-and-Pixma-iP1000-iP1500.html</link>
            <category>Debian</category>
            <category>Linux</category>
    
    <comments>http://cryingwolf.net/archives/86-Debian-packages-for-Canon-Pixus-iP3100-ip4100-ip8600-and-Pixma-iP1000-iP1500.html#comments</comments>
    <wfw:comment>http://cryingwolf.net/wfwcomment.php?cid=86</wfw:comment>

    <slash:comments>6</slash:comments>
    <wfw:commentRss>http://cryingwolf.net/rss.php?version=2.0&amp;type=comments&amp;cid=86</wfw:commentRss>
    

    <author>nospam@example.com (NickNack)</author>
    <content:encoded>
    &lt;br /&gt;I recently setup a Canon iPIXMA Printer on Debian Sarge, quite a pain &lt;img src=&quot;&quot; alt=&quot;:-D&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;
&lt;br /&gt;but thanks to this package and HOWTO from Takushi Miyosh from Japan
&lt;br /&gt;really save my day ( and night ! )
&lt;br /&gt;
&lt;br /&gt; &lt;br /&gt;&lt;a href=&quot;http://cryingwolf.net/archives/86-Debian-packages-for-Canon-Pixus-iP3100-ip4100-ip8600-and-Pixma-iP1000-iP1500.html#extended&quot;&gt;Continue reading &quot;Debian packages for Canon Pixus iP3100 / ip4100 / ip8600 (and Pixma iP1000 / iP1500)&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Tue, 20 Dec 2005 02:47:00 +0700</pubDate>
    <guid isPermaLink="false">http://cryingwolf.net/archives/86-guid.html</guid>
    
</item>

</channel>
</rss>