Echolot snapshot 2003-02-25

[Peter Palfrader]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've uploaded a snapshot release for Echolot.  Assuming there are no
evil bugs this will become 2.1 eventually, but I certainly want more
testing before releasing it as that.

The 2003-02-25 snapshot introduces several new features, of which
automated chain pinging is only one.

Here's the relevant part from the NEWS file:

        * Minor documentation fixes suggested by Ryan Lackey.
        * Adjusted some loglevels (several info got downgraded to debug)
        * Removed --pgp2 in CPunk RSA pings.
        * Append random garbage to pings so they have different
          lengths.
          new options:
            - random_gabage (default: 8192)
              Garbage length is chosen uniformly from 0 to random_gabage
              bytes.
            - dev_urandom (default: /dev/urandom)
              where to read garbage from (more generally: non-blocking
              (low-quality) randomless source)
        * Chain pinging:  Echolot now finds broken chains.
          new options:
             - do_chainpings (default: 1)
               Whether to do chain pinging.
             - show_chainpings (default: 1)
               Whether to show the result of our chain pinging in the
               public stats.
           Several other settings control the details of chain pinging.
           You probably don't want or need to tweak them. See
           the pingd.conf(5) manual page for details.
           - Also adds the new "sendchainpings" command.
        * Create an index.txt file in the thesaurus directory which
          holds id, nick, and address for each remailer in the thesaurus.
          This helps additional tools to utilize Echolot's data.
        * Compile a list of default From: lines as well as a list of
          remailers which allow user supplied From headers.
        * Print status summary to log daily.
           - Also adds the new "summary" command.
        * Reliable and CRLF - a neverending (sad) story.
        * Handle situations better in which a ping is receiverd when the
          key already is expired.

I would welcome your feedback especially on the chain pinging.  Perhaps
you want to set the following option while trying it:

        show_chainpings => 0,

This will make the results of chain pinging only available in the
results.private/ stats.  In the log you can see various additional
info about the chains at DEBUG level.


You can find it at the usual place:
 http://savannah.gnu.org/download/echolot/echolot-snapshot-2003-02-25.tar.gz
   Size/MD5 checksum:    99393 1c7b6cab3cbd5834aa9ae0d56c06b052
 http://savannah.gnu.org/download/echolot/echolot-snapshot-2003-02-25.tar.gz.asc
   Size/MD5 checksum:      192 73fe37bb18ba158225c74926af0afa52

Peter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2rc1 (GNU/Linux)

iD8DBQE+W/BH3nqvbpTAnH8RAizGAJ97LKqyCrKgXEGRj/uBNUXeL7asNwCeM27R
xZxZWp683DJgC/JujAfPZd0=
=aYf2
-----END PGP SIGNATURE-----