| Name | Last modified | Size | Description | |
|---|---|---|---|---|
| RBL-check.pl-v227 | 2008-07-24 23:02 | 19.4K | Mail-server is on RBL ob.nox.ious | |
| RBL-check.pl-v227.asc | 2008-07-24 23:03 | 163 | PGP Signature | |
| RBL-check.pl.changelog.txt | 2008-07-24 23:05 | 4.2K | Revision history | |
| RPMs | 2012-05-19 08:54 | - | ||
| desktop-notify.pl-v0.3 | 2009-11-11 09:31 | 9.4K | Irssi DBUS notification plugin | |
| emit_ipv6_regexp-0.304 | 2010-01-03 02:43 | 4.3K | IPv6 RegExp emitter | |
| emit_ipv6_regexp-0.304.asc | 2010-01-03 02:43 | 163 | PGP Signature | |
| mailcheck-imap-0.406.tar.bz2 | 2010-08-14 06:22 | 59.6K | You have 2 new mails in INBOX | |
| mailcheck-imap-0.406.tar.bz2.asc | 2010-08-14 06:22 | 163 | PGP Signature | |
| mailcheck-imap.ChangeLog.txt | 2010-08-14 06:22 | 89.4K | Revision history | |
| puny.py-v458 | 2011-02-06 23:44 | 4.7K | ||
| puny.py-v458.asc | 2011-02-06 23:44 | 163 | PGP Signature | |
| sieve-connect-0.81.tar.bz2 | 2011-04-02 10:10 | 30.0K | Client for the MANAGESIEVE protocol | |
| sieve-connect-0.81.tar.bz2.asc | 2011-04-02 10:10 | 163 | PGP Signature | |
| sieve-connect.ChangeLog.txt | 2011-04-02 10:10 | 19.5K | Revision history | |
| sks_peers.py-v285 | 2011-05-20 09:49 | 82.7K | SKS mesh mapper | |
| sks_peers.py-v285.asc | 2011-05-20 09:49 | 163 | PGP Signature | |
| sks_peers.py.ChangeLog.txt | 2011-09-08 22:42 | 25.8K | Revision history | |
| smtp_tls_cert.pl | 2008-06-15 01:00 | 3.8K | Dump PEM-encoded TLS cert from MSA server | |
If a version number is encoded as -v<wholenum> then it's not directly the version of the software, it's the version of the repository I keep it in; the number will only ever go up, but there will be lots of missing intermediate values. Really, this is because I'm lazy.
You should be able to figure out a contact email address from reading whichever script you're looking at. Hints include the usercode used for SVN access and the domain of the web-server you're looking at (at the WHOIS registration level). If you want a PGP-signed sig where not already provided, ask. At the moment, most of these are scripts intended for people to read and check over, rather than just trust.
Whilst this server should also normally be available via https://, I do not normally purchase certificates from any widely distributed CA. The certificate in use is from my own personal CA, which is probably not suitable for general use. If you're interested in getting the CA cert and using HTTPS, then the cert and a PGP-signature can be obtained from www.security.spodhuis.org. That site does have a cert from a widespread PKI. Note that the Opera web-browser allows you to mark a CA certificate with a “warn me when this cert is used” flag.
If a changelog file is not up-to-date, prod me. I need to make them automatic.
Note that the above list of files is not complete; older versions exist in this directory, but aren't shown so as to reduce clutter.
If you have IPv6 connectivity then you'll be able to make use of the publicly available svn repository. It's browseable at http://svn.spodhuis.org/viewvc/ and can be checked out under /svn/. IPv6-only as I use Kerberised access and only have enough IP addresses for Kerberisation with dedicated service hostnames (as in, web vhosts) if I use IPv6.
I attempt to provide extended HTTP headers in the response, to aid in verification of retrieved files; there is a small chance that I've either made a mistake in how these are generated, or that their presence will lead to interoperability issues; if you encounter such problems, please do contact me to report the problem so we can work together to fix it. In particular, I provide the Content-MD5:, Digest: (SHA-256) and Link: headers.