--- trunk/Mix/HISTORY 2002/12/28 02:05:32 449 +++ trunk/Mix/HISTORY 2004/04/22 00:38:21 760 @@ -283,7 +283,7 @@ Minor code formating cleanup and Install script fixes. -2002-xx-xx STABLE The Mixmaster protocol version is now prepended +2002-12-15 2.9b41 The Mixmaster protocol version is now prepended to the software version in the Mixmaster cap- string. Minor configuration default changes and Install @@ -303,15 +303,36 @@ submitted by Trek. Vulnerability originally discovered by noise and rabbi.) Minor documentation fixes. + +2002-12-16 2.9b42 Minor documentation fixes. Append another newline character to mbox folders when storing a mail so that the mandatory empty line is there. -2002-10-18 3.0a1 Applied Maildir feature patch by drt@un.bewaff.net, - with some changes by PP: - MAILBOX can now be a Maildir (closes: #586223). - Mixmaster in daemon mode reloads configuration on - SIGHUP. +2002-12-16 2.9.0rc1 Release candidate. Packaging changes only. + +2002-12-25 2.9.0 Release version. Minor documentation changes + and version number change only. + +2003-11-08 2.9.1 Several changes for the Windows build. + Some Install script fixes. + Fixed a problem in blockrequest() where a buffer + could have been used after it was free()'d which + resulted in segfaults. + Check that feedback buffer is not null before + operating on it in chain_select(). + Closes #631353, thanks Sami Farin. + Make sure DH/DSA param file is actually opened + before writing to it. Fixes a segfault in + case it is not. + Handle a pool we cannot read correctly: don't close + the NULL dir handle (segfaults on *BSD). We also + print a warning in that case now. + Minor stats fix (gmtime vs localtime). + Fix pool stats bug. + +2004-03-20 3.0b1 FEATURE ENHANCEMENTS: + The secret pgp keyring is now stored ASCII armored with one key per ascii armor. NB: Due to the bug with reading armored keyrings and @@ -326,12 +347,12 @@ Mixmaster will not encrypt or sign with a revoked or expired key. When encrypting, Mixmaster uses preferences from - the primary userid (or the latest userid, if zero - or more than one primary userid is present.) + the primary userid (or the latest userid, if zero + or more than one primary userid is present.) Mixmaster keys now have creation and expiration date. It is not secured by any crypto voodoo, it's only informational for clients to decide which keys to - use should they have more. + use should they have more than one per remailer. - on the client side we do not show remailers (and therefore not use them) if their key is expired. - the remailer refuses to decrypt messages to keys @@ -345,12 +366,92 @@ seemed sensible. Mixmaster now generates dummy messages automatically as mail enters and exits the pool. - -2002-xx-xx 3.0a2 New Star-Exclude feature by Colin Tuckley: + Applied Maildir feature patch by drt@un.bewaff.net, + with some changes by PP: + MAILBOX can now be a Maildir (closes: #586223). + New Star-Exclude feature by Colin Tuckley: User-selected remailers can be excluded from being chosen as random hops. Have stats on intermediate vs. final hop count (closes: #649900). - Handle a pool we cannot read correctly: don't close - the NULL dir handle (segfaults on *bsd). We also - print a warning in that case now. + Add max capability for Type I. + Config option EXTFLAGS allows appending additional + flags to the capabilities string. (Hauke Lampe) + Config option PRECEDENCE allows setting the + Precedence: header on all outgoing mail. + (Hauke Lampe) + In order to serve help files in different languages + we need a way to reply to requests like + remailer-help-it. In order to not have to modify + the code for each and every new ressource, + Mixmaster now sends the file + requests/remailer- to + remailer- requests. + remailer-{help,key, stats,conf,adminkey} still are + special cases tho. + Drop messages without timestamps and messages with + future timestamps. This abandons backwards + compatibility with Mixmaster 2.0.3 and earlier. + Mixmaster attempts to detect system clock + misconfigurations and refuses to run as a + remailer if there is a problem suspected. + Only applies to Mixmaster in remailer mode. + + BUG FIXES: + + Mixmaster in daemon mode reloads configuration on + SIGHUP. + In the curses interface chain selection it was not + possible to select a random last hop with a usenet + post message. Fixed (closes: #719165). + If remix was enabled and we had a Type-I Anon-Post-To + request we accidently randhoped it via the + configured default remailing chain (default: + *,*,*,*). + Fixed (closes: #729494). + In client mode (REMAIL n) the pool is flushed every + time mixmaster is run unless CLIENTAUTOFLUSH is + set to n. (closes: #676794: Rate implementation + doubled) + Found that weird bug that sometimes led to "Unknown + remailer version!" errors: In chain_randfinal() we + selected a random value between 0 and maxrem + instead of 0 and maxrem - 1. Mixmaster now uses + broken-chain info from stats. I hope this doesn't + break any Nym functionality. + Warn if remailer stats are older than a day or + from the future. + Don't send messages to ourselves via the mailsystem + but instead place them in the pool as incoming + messages so that they will get processed with the + next pool run. + No longer try to send a message if there are no + recipients left. + Set default max-randhops from 20 to 4. + Remix-To chain is limited by max-randhops limit as + well. + Messages to more than one remailer are dropped. + Nym support is not compiled in by default anymore. + The OpenPGP module mpgp now includes a man + page (large contributions by Trek). + Ignore 'No reliable remailers' problems when + randhopping messages in middleman mode. + That is better than dropping them. + Experimental feature: --redirect -l . + If you have a mixmaster message with a + chain starting with hop1 (you cannot know any + more because it already is encrypted) then + mix --redirect -l foo,bar < file + redirect the message so the chain is actually + foo,bar,hop1,... and places it in your pool. + If the total number of hops (which cannot be + known) exceeds 20 the message is damanged + and will fail at the 20th node. + +2004-03-20 3.0b2-unreleased + Use /dev/arandom instead of /dev/srandom on + OpenBSD (Nikolay Sturm). + Fall back to 3DES as Encrypt-Key cipher if we don't + have IDEA. - Laurent Fousse + Also sort mail into the various mboxes if autoreply + is not set.