Parent Directory | Revision Log
|Links to HEAD:||(view) (download) (annotate)|
Set keyword expansion for Id on all files that already have $Id$ tags.
Do away with the conditional use of RSA, always using it. Without RSA we aren't much good anyway.
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
Forgot to rewind the buffer
Only return latest pgp keys to remailer-key requests
Write keyid, creation date, etc header along with armored keys to pgpkey.txt
Do not recreate the public keys from the private keyring if there still is a public keyring in pgpkey.txt. This means we don't recreate the self signature on binding keys amoung other things. It probably also means that one can replace the keys in pgpkey.txt with keys signed by the adminkey and not have them overriden the next time one does ./mix -[GK] (although I did not test this). We still need to fix keymgt to only return the latest keys - this should be simple once I find out how to get expiration date for a specific key. There's a small problem with the current keymanagement for PGP keys I guess. If the latest key is not the last in the keyring we might screw up. Can you verify this Disastry?
Make sure to always have the right one of begin private/public key
Reverse that - I'll do it differently
pass armortype to pgpdb_close - used when file needs to get armored
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.
Move table heads to their right place. i.e. one char to the right
check expiration and revocation of pgp keys, userids, subkeys do not encrypt with expired or revoked keys, subkeys do not sign with expired or revoked keys do not decrypt with expired keys, subkeys after graceperiod when encrypting use preferences from latest and/or primary userid create new pgp keys if current are to expire in overlapperiod
Fixed a bug with reading armored keyrings consisting of more than one armored block or having comments in front of the one armored block. 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 secring being stored armored now, it is not adviseable to downgrade mixmaster unless special action is taked to preserve the secret pgp keyring.
Use names rather than numbers as arument to pgp_armor. Have PGP PRIVATE for armoring
Also list cypherpunk remailers in remailer-conf reply. Thanks to Ulf and Disastry for their help.
Mixmaster now uses the OpenPGP MDC packets (as specified in RFC 2440-bis06). Mixmaster will use MDC packets if the MDC flag is found in the recipient's PGP key, or by default if it is encrypting with AES. New keys generated with Mixmaster will have the MDC flag placed in the key's preferences. Also, cipher preferences are now advertised as CAST5, AES128, 3DES.
Fix public remailer keys getting re-signed every time keys are requested (Closes: #478383).
Only create OpenPGP RSA keys if we compiled with IDEA.
We have changed the compile-time option PASSPHRASE to be named COMPILEDPASS. We have changed the configuration file option PASS_PHRASE to be named PASSPHRASE. We have added documentation for the new configuration file option and made changes in the man page to reflect the name change. This was done to avoid confusion due to the similarity in names of the options.
Added the ability to store the key passphrase in the mix.cfg file instead of having it compiled into the binary. This offers a number of advantages over the compiled-in method and still allows for encrypted remote storage of keys. In order to take advantage of the new changes, the Install script will need to be modified. As this is being replaced with a proper autoconf system, we're defering that until later. The changes we're committing replace PASSPHRASE with PASS_PHRASE, which is read from the config. If the compiled-in passphrase, PASSPHRASE, is set, that is used instead. (This is how Mixmaster will function if you use the Install script.)
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|