<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Tanguy Ortolo - Lazyweb</title>
	<link>https://tanguy.ortolo.eu/blog/categorie15/lazyweb</link>
	<language>en</language>
	<description>a blog about Debian and self-hosting</description>
<atom:link xmlns:atom="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="https://tanguy.ortolo.eu/blog/feed.php" />
	<lastBuildDate>Thu, 31 Oct 2013 15:51:00 +0000</lastBuildDate>
	<generator>PluXml</generator>
	<item>
		<title>How to implement a Postfix spam trap?</title> 
		<link>https://tanguy.ortolo.eu/blog/article114/postfix-spamtrap</link>
		<guid>https://tanguy.ortolo.eu/blog/article114/postfix-spamtrap</guid>
		<description>&lt;a href=&quot;http://tango.freedesktop.org/&quot; title=&quot;From the Tango Desktop Project, Public Domain&quot;&gt;&lt;img src=&quot;https://tanguy.ortolo.eu/blog/data/images/icons/tango-email-128.png&quot; alt=&quot;Open envelope&quot; style=&quot;float: right; margin-top: 2em;&quot;/&gt;&lt;/a&gt;

&lt;h2&gt;Spam trap&lt;/h2&gt;

&lt;p&gt;Dear lazyweb, I am considering to implement spam traps and evaluate
their efficiency. The idea as rather simple:&lt;/p&gt;

&lt;ol&gt;
    &lt;li&gt;publish some real-looking email addresses on websites, in ways
    that no human would use them to send legitimate mail, for instance
    in hidden texts, or in texts clearly stating they should not be
    used;&lt;/li&gt;
    &lt;li&gt;when my mail server receives a message for one of these address,
    blacklist the originating server for some time so it cannot spam
    real recipients.&lt;/li&gt;
&lt;/ol&gt;&lt;h2&gt;Practical implementation&lt;/h2&gt;

&lt;p&gt;Now, I have to decide on how to implement that with my Postfix 
server. I am thinking of using fail2ban to simply detect attempts to 
send mail to my spam traps and blocking these spammers at
iptables-level, but I do not think that will give me much tuning
possibilities. Do you have other suggestions?&lt;/p&gt;

&lt;h2&gt;Implementation details&lt;/h2&gt;

&lt;p&gt;I also have to think about some specific details. Here is what I
identified so far, do you think I am missing something that may be
useful?&lt;/p&gt;

&lt;ul&gt;
    &lt;li&gt;Blacklisting time: since no legitimate mail can ever be sent to
    an explicit spam trap address, everyone sending mail to these
    addresses is by definition a spammer, so I can block them for
    months, if not forever. There is, however, a risk of blocking large
    scale services mostly used by regular users but sometimes abused by
    spammers, like Hotmail or Gmail…&lt;/li&gt;
    &lt;li&gt;Server response: a spam trap address is only efficient if it
    gets included in a spammer&#039;s address list and if it stays there, so
    I should make sure my server answers the first attempt in a way that
    does not make him think that address is problematic and should be
    removed from his list. Defining a &lt;code class=&quot;filename
        device&quot;&gt;/dev/null&lt;/code&gt; alias should do it.&lt;/li&gt;
&lt;/ul&gt;</description>
		<pubDate>Thu, 31 Oct 2013 15:51:00 +0000</pubDate>
		<dc:creator>Tanguy</dc:creator>
	</item>
	<item>
		<title>Looking for an SPF milter</title> 
		<link>https://tanguy.ortolo.eu/blog/article103/spf-milter</link>
		<guid>https://tanguy.ortolo.eu/blog/article103/spf-milter</guid>
		<description>&lt;a href=&quot;http://tango.freedesktop.org/&quot; title=&quot;From the Tango Desktop Project, Public Domain&quot;&gt;&lt;img src=&quot;https://tanguy.ortolo.eu/blog/data/images/icons/tango-email-128.png&quot; alt=&quot;Envelope&quot; style=&quot;float: left; margin-top: 1em;&quot; /&gt;&lt;/a&gt;

&lt;p style=&quot;margin-top: 2em;&quot;&gt;For email extensions such as SPF, DKIM and DMARC, I think the most
flexible and portable system is the milter protocol. Originally
developed for Sendmail, it is now also supported by Postfix, and it
allows to “plug” specific filters in the mail server without the hassle
of the previous systems like SMTP proxies.&lt;/p&gt;&lt;h2 style=&quot;clear: both;&quot;&gt;SPF milters in Debian&lt;/h2&gt;

&lt;p&gt;OpenDKIM provides a good milter for checking DKIM. OpenDMARC provides
a similar milter for DMARC. But the situation is more difficult for SPF
in Debian — which is a requirement for DMARC! :&lt;/p&gt;

&lt;dl&gt;
    &lt;dt&gt;spf-milter&lt;/dt&gt;
    &lt;dd&gt;It was based on the buggy libspf0 and was never updated to
    libspf2, and was finally removed from Debian;&lt;/dd&gt;
    &lt;dt&gt;spf-milter-python&lt;/dt&gt;
    &lt;dd&gt;This one seems a bit Sendmail-centric — it uses a dbm
    configuration file for instance — and not very documented.&lt;/dd&gt;
&lt;/dl&gt;

&lt;h2&gt;Packaging a new SPF milter?&lt;/h2&gt;

&lt;p&gt;There are other milters for SPF, which have not been packaged for
Debian yet, but I am ready to package one. Has anybody tried another SPF
milter?&lt;/p&gt;

&lt;dl&gt;
    &lt;dt&gt;&lt;a
        href=&quot;http://www.acme.com/software/spfmilter/&quot;&gt;spfmilter&lt;/a&gt;&lt;/dt&gt;
    &lt;dd&gt;Still in beta test, still to be ported to libspf2 which may
    never happen since it was not updated since 2005.&lt;/dd&gt;
    &lt;dt&gt;&lt;a href=&quot;http://sourceforge.net/projects/smfs/&quot;&gt;smf-spf&lt;/a&gt;&lt;/dt&gt;
    &lt;dd&gt;Based on libspf2, seems rather neat, with a clean configuration,
    but inactive since 2007.&lt;/dd&gt;
    &lt;dt&gt;&lt;a
        href=&quot;http://www.snertsoft.com/sendmail/milter-spiff/&quot;&gt;milter-spiff&lt;/a&gt;&lt;/dt&gt;
    &lt;dd&gt;Proprietary.&lt;/dd&gt;
&lt;/dl&gt;</description>
		<pubDate>Fri, 07 Jun 2013 18:14:00 +0000</pubDate>
		<dc:creator>Tanguy</dc:creator>
	</item>
	<item>
		<title>Camera with a standard USB cable?</title> 
		<link>https://tanguy.ortolo.eu/blog/article49/camera-usb</link>
		<guid>https://tanguy.ortolo.eu/blog/article49/camera-usb</guid>
		<description>&lt;img src=&quot;https://tanguy.ortolo.eu/blog/data/images/icons/tango-camera-128.png&quot; alt=&quot;Digital camera icon&quot; title=&quot;From the Tango Desktop Project, Public Domain&quot; style=&quot;float: left; margin-right: 1em;&quot; /&gt;

&lt;p&gt;Since some years, there has been a movement towards standardization: mobile
devices are now using Micro-USB for data transfer and charging, and SD or
Micro-SD for storage extension (except Apple of course).&lt;/p&gt;

&lt;p&gt;One piece is lacking to this perfection, however; as far as I know, digital
camera producers did realize that SD won for storage, but they do not seem to
have acknowledged the Micro-USB standard yet.&lt;/p&gt;

&lt;p&gt;Now, since manufacturers and resellers do not indicate the connector type, I
have no way to be sure that this is still the case. So, dear lazyweb, do you
know if, by chance, there exists a compact digital camera that would use SD
cards and a Micro-USB connector for data transfer and integrated charging?&lt;/p&gt;</description>
		<pubDate>Tue, 17 Apr 2012 19:01:00 +0000</pubDate>
		<dc:creator>Tanguy</dc:creator>
	</item>
	<item>
		<title>Opportunistic SSH agent</title> 
		<link>https://tanguy.ortolo.eu/blog/article43/opportunistic-ssh-agent</link>
		<guid>https://tanguy.ortolo.eu/blog/article43/opportunistic-ssh-agent</guid>
		<description>&lt;p&gt;To use an SSH agent, one usually has to:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;launch the agent;&lt;/li&gt;
    &lt;li&gt;add his key to it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The first step can be automated in the desktop or &lt;a
href=&quot;../article25/shrc&quot;&gt;shell startup script&lt;/a&gt; (this is a typical use case for
login shell-only startup scripts, by the way), but the second one cannot if your
private key is protected by a passphrase.&lt;/p&gt;&lt;h2&gt;Opportunistic key loading&lt;/h2&gt;

&lt;p&gt;&lt;a href=&quot;http://live.gnome.org/GnomeKeyring&quot;&gt;GNOME Keyring&lt;/a&gt; includes an &lt;a
href=&quot;http://live.gnome.org/GnomeKeyring/Ssh&quot;&gt;SSH agent&lt;/a&gt; which has an
interesting feature I call “opportunistic key loading”: it asks for the
passphrase to decrypt the private key the first time it is needed. This feature
mimics the behaviour of PGP agents, and eliminates the second step I previously
mentioned.&lt;/p&gt;

&lt;h2&gt;Question&lt;/h2&gt;

&lt;p&gt;Do you know if there exists another SSH agent able to do opportunistic key
loading?&lt;/p&gt;</description>
		<pubDate>Mon, 20 Feb 2012 13:19:00 +0000</pubDate>
		<dc:creator>Tanguy</dc:creator>
	</item>
</channel>
</rss>