Log of /trunk/Mix/HISTORY
Parent Directory
| 
Revision Log
Revision
214 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Thu Sep 5 01:21:54 2002 UTC
(10 years, 8 months ago)
by
weaselp
File length: 16233 byte(s)
Diff to
previous 203
,
to
selected 93
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.
Revision
187 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Mon Aug 26 19:37:43 2002 UTC
(10 years, 8 months ago)
by
rabbi
File length: 14874 byte(s)
Diff to
previous 185
,
to
selected 93
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.
Revision
185 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Mon Aug 26 19:17:31 2002 UTC
(10 years, 8 months ago)
by
weaselp
File length: 14642 byte(s)
Diff to
previous 184
,
to
selected 93
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.
Revision
170 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Thu Aug 22 06:22:56 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 13452 byte(s)
Diff to
previous 168
,
to
selected 93
When expiring packet ids from id.log also expire packets that are dated more
than half a year in the future. That way we get rid of invalid packets
introduced by the switch to a binary file.
Revision
168 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Thu Aug 22 05:18:26 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 13146 byte(s)
Diff to
previous 166
,
to
selected 93
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?
Revision
165 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Thu Aug 22 04:01:16 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 12850 byte(s)
Diff to
previous 163
,
to
selected 93
When sending type II messages interactivly you may now choose a middleman
remailer as the last hop in your chain (closes: #481244).
Revision
163 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Wed Aug 21 19:28:04 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 12633 byte(s)
Diff to
previous 159
,
to
selected 93
Make sure to deliver to the right directory with Maildir deliveries. Since
we do not chdir() to the Mixmaster base directory we need to take care of
this whenever we do file or directory operations. Fortunatly the function
mixfile() helps here. mixfile() was extended to handle paths starting
with "~/". '~' is replaced by the HOME environment variable if defined.
Implement MAILIN option: If set Mixmaster reads mails from either a mbox
or a Maildir mail folder when processing its queue (-M or daemon). After
reading the mail folder is emtpied. If MAILIN ends with / it is expected
to be a Maildir, mbox oterhwise.
I hope that I did not break anything with the change to mixfile(). Maildir
drop and reading from both Maildir and mbox has been tested a little. Seems
to work fine so far.
Revision
159 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Wed Aug 21 16:03:12 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 12337 byte(s)
Diff to
previous 153
,
to
selected 93
Secret plan to get rid of IDEA stage (1):
The Install script detects - in a reliable fashion - whether idea support
is available. It only defines USE_IDEA if this is the case. On operating
systems that lack the patented IDEA algorithm (OpenBSD and Debian for
instance) a warning is printed but building and installation is not
halted.
Revision
135 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Fri Aug 16 19:03:37 2002 UTC
(10 years, 9 months ago)
by
rabbi
File length: 11840 byte(s)
Diff to
previous 134
,
to
selected 93
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.
Revision
120 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Sat Aug 3 17:08:02 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 11006 byte(s)
Diff to
previous 119
,
to
selected 93
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().
Revision
116 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Mon Jul 29 23:52:00 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 10909 byte(s)
Diff to
previous 115
,
to
selected 93
Make smtp sending similar to local /usr/lib/sendmail sending (wrt header/body seperation; Closes: #482052).
Add X-Loop header on mailbox forwarded messages.
Revision
101 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Wed Jul 24 07:00:16 2002 UTC
(10 years, 10 months ago)
by
rabbi
File length: 9685 byte(s)
Diff to
previous 99
,
to
selected 93
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.
Revision
93 -
(
view)
(
download)
(
annotate)
-
[selected]
Modified
Thu Jul 11 02:39:33 2002 UTC
(10 years, 10 months ago)
by
rabbi
File length: 8989 byte(s)
Diff to
previous 91
Modified the Install script to properly locate opensslv.h. It now checks
in both $INCDIR/openssl and $INCDIR/ for the file.
Also, I reverted back to the version checking that was done in 2.9beta23,
and added special case exceptions for the four OpenSSL versions with
alphanumeric designations prior to the main version check, since Bourne
shell cannot handle multiple bases and bash is not universal.
Also,I modifed the "upgrade" script for clarity, and changed the default
from "y" to "n" for activating Type I remailers on installation.
Lastly, I performed pre-release configuration file updates. Ready for
2.9b35.
Revision
91 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Wed Jul 10 01:58:49 2002 UTC
(10 years, 10 months ago)
by
rabbi
File length: 8748 byte(s)
Diff to
previous 90
,
to
selected 93
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.)
Revision
57 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Mon Dec 17 03:16:48 2001 UTC
(11 years, 5 months ago)
by
rabbi
File length: 7970 byte(s)
Diff to
previous 42
,
to
selected 93
Fixed inconsistencies between software name and package name. This was
done for compatability with automated install tools as well as for
consistancy. Archive is now named mixmaster-2.9b33.tar.gz and archive
directory is now named mixmaster-2.9b33.
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.
