Parent Directory | Revision Log
|Links to HEAD:||(view) (download) (annotate)|
Mixmaster now prompts for user input for the secret key passphrase when mix is started in daemon mode (./mix -D). Mixmaster will try to find either PGP/RSA, PGP/ELG or Mix key that can be decrypted with the provided passphrase. If it finds one, it assumes the passphrase is good. (We may have a problem if the user manages to get his secret key passphrases out of sync. Suggestions on handling this case?) FYI: the passphrase in mix.cfg takes precedence over the passphrase compiled into the binary. If neither of these are present, only then is the user prompted for a keyboard-input passphrase. We still need to make mix retain the user-provided passphrase across SIGHUP signals.
Make sure files are closed
Submitted By: Sami Farin (safari): Included correct header files. Src/main.c had incorrect param to buf_appendf. Added buf_write_sync() (used by Src/rem.c:mix_pool()). Should a mixmaster machine crash, pool file can contain any random data after reboot/journal recovery (at least when using reiserfs). Maybe not relevant, but strrchr should be used instead of strchr when looking for domain part. Src/pgpdata.c:pgp_elgdecrypt() passes uninitialized values to BN_free if BN_CTX_new fails. Src/pgpdata.c:pgp_elgencrypt() passes uninitialized value to BN_free if the third mpi_get(key, i) fails. Src/random.c does not check return value of read(). Src/rndseed.c does not check return value of read().
The -G option now forces creation of new keys even in client mode (Closes: #585176)
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.)
Mixmaster now does not attempt to generate keys when run in client-only mode (REMAIL set to "n") as there is no reason to do so. Requested by Richard Christman for Quicksilver.
Put "M" in key file (key.txt) if remailer is middleman. (disastry) Remember the flags are: C accepts compressed messages. M will forward messages to another mix, when used as the final hop. Nm supports posting to Usenet throught a mail-to-news gateway. Np supports direct posting to Usenet.
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|