Parent Directory | Revision Log
|Links to HEAD:||(view) (download) (annotate)|
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
Write keyid, creation date, etc header along with armored keys to pgpkey.txt
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.
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
When creating new OpenPGP keys, also set an expiry date. Key lifetime defaults to 8 months but can be overriden by the KEYLIFETIME configuration option. We currently do not store the self signature and the keybinding (which hold the expiry information in DSA keys) in the secret keyring. This is unfortunate because we use the current KEYLIFETIME when recreating them should the public keyring need to be rewritten. The solution is to store them in the secret keyring (like GnuPG does) and not recreate them later if we already have them.
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.
Formatting corrections. Now prints Mixmaster version in the OpenPGP Version header when displaying a normal PGP message or key. (Either outputs "Version: N/A" or "Version: 2.6.3i" when formatting remailer or nym messages. Should we make this a user-configurable option?)
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.
Added support for Sym. Encrypted Integrity Protected Data Packet (Tag 18) and Modification Detection Code Packet (Tag 19) in the OpenPGP code. See RFC2440bis-05:5.13 for more info. Mixmaster's PGP functionality and mpgp both need extensive compatibility and regression testing now.
Add info to #endifs stating to which #if they belong
Added support for AES in Type I messages. This should prevent lost mail if a user attempts to send OpenPGP messages encrypted with AES. Support for AES requires OpenSSL 0.9.7 (soon to be released.) The Install script needs to be updated to enable AES if 0.9.7 or later is present. Also, pgp_keylen now returns 0 instead of -1 for unknown symalgo. Output of pgp_keylen is used in buf_appendrnd and in other functions without checking, so they might be unhappy with -1. (We should really check for this.) Thanks to Disastry and Peter for working on this.
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|