Parent Directory | Revision Log
|Links to HEAD:||(view) (download) (annotate)|
Updated copyright dates.
Added new config directive MINLAT. Remailers will not be chosen in the path for dummy messages or random hops unless their latency is greater than or equal to the MINLAT value. (Default: 5 minutes.) This is a precautionary measure against broken remailers. It does not affect currently operating remailers at this time. Suggested by Zax. (Closes #1241903).
Ignore type2.list (always use pubring)
Updated copyright dates, doc issues, misc fixes.
Also warn if Remailer Reliability Statistics are from the future. Also accept rfc822 style dates
Set keyword expansion for Id on all files that already have $Id$ tags.
Ignore 'No reliable remailers' problems when randhopping messages in middleman mode. That is better than dropping them.
Do away with the conditional use of RSA, always using it. Without RSA we aren't much good anyway.
Experimental feature: --redirect -l <chain>. 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.
Have mixmaster build with gcc 2.95 again
Respect DISTANCE setting also when selecting the final hop. This is important in cases where the user chooses a chain like '*,*,valiant,*'. Previously it was possible that valiant was taken as a last hop resulting in a chain like '....,valiant,valiant'.
Warn if stats are older than one day
Mixmaster now uses broken-chain info from stats. I hope this doesn't break any Nym functionality.
Applied Colin's star exclude patch
Whitespace cleanup: for i in *.c; do cp -a $i $i.orig; sed -e 's/^ /<TAB>/' $i.orig > $i; rm $i.orig; done for i in *.c *.h; do cp -a $i $i.orig; sed -e 's/[ <TAB>]*$//' $i.orig > $i; rm $i.orig; done
Added closing comments for all #ifdef statements. All #endif's, as well as nested braces, should be commented to reference their start. We need to provide comments before every function as well.
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. - 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 that expired one month ago or earlier. - the remailer automatically creates new mixmaster keys if the current one are about to expire or already are expired. - the latest key from secring.mix is written to key.txt. It used to be the first one. Since creation of new mix key appends the key, this seemed sensible.
List known mixmasters in remailer-conf replies. How do I get a list of the pgp keyring so I can also list type I remailers? Do we need to list type I remailers?
The -T option (display type2.list) previously would not work if the file type2.list was not present. -T will now display type2.list info retrieved from pubring.mix if type2.list is not present.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
|Powered by ViewVC 1.1.5|