You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(13) |
---|
From: <bfo...@us...> - 2002-12-19 23:33:27
|
Update of /cvsroot/mixlet/mixlet/src/cryptix/util/core In directory sc8-pr-cvs1:/tmp/cvs-serv9304/core Log Message: Directory /cvsroot/mixlet/mixlet/src/cryptix/util/core added to the repository |
From: <bfo...@us...> - 2002-12-19 23:33:05
|
Update of /cvsroot/mixlet/mixlet/src/cryptix/provider/key In directory sc8-pr-cvs1:/tmp/cvs-serv8958/key Log Message: Directory /cvsroot/mixlet/mixlet/src/cryptix/provider/key added to the repository |
From: <bfo...@us...> - 2002-12-19 23:33:05
|
Update of /cvsroot/mixlet/mixlet/src/cryptix/provider/md In directory sc8-pr-cvs1:/tmp/cvs-serv8958/md Log Message: Directory /cvsroot/mixlet/mixlet/src/cryptix/provider/md added to the repository |
From: <bfo...@us...> - 2002-12-19 23:33:05
|
Update of /cvsroot/mixlet/mixlet/src/cryptix/provider/cipher In directory sc8-pr-cvs1:/tmp/cvs-serv8958/cipher Log Message: Directory /cvsroot/mixlet/mixlet/src/cryptix/provider/cipher added to the repository |
From: <bfo...@us...> - 2002-12-19 23:32:54
|
Update of /cvsroot/mixlet/mixlet/src/xjava In directory sc8-pr-cvs1:/tmp/cvs-serv8750/xjava Log Message: Directory /cvsroot/mixlet/mixlet/src/xjava added to the repository |
From: <we...@us...> - 2002-12-19 22:15:25
|
Update of /cvsroot/mixlet/CVSROOT In directory sc8-pr-cvs1:/tmp/cvs-serv24521 Modified Files: loginfo Log Message: Use the sane unified diff format rather than this ugly context diff Index: loginfo =================================================================== RCS file: /cvsroot/mixlet/CVSROOT/loginfo,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** loginfo 19 Dec 2002 20:57:29 -0000 1.2 --- loginfo 19 Dec 2002 22:15:22 -0000 1.3 *************** *** 25,27 **** # or #DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog ! DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} mix...@li... --- 25,27 ---- # or #DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog ! DEFAULT $CVSROOT/CVSROOT/syncmail -u %{sVv} mix...@li... |
From: <bfo...@us...> - 2002-12-19 21:48:42
|
Update of /cvsroot/mixlet/mixlet/src In directory sc8-pr-cvs1:/tmp/cvs-serv9497 Modified Files: MixEncryptedHeaderPart.java MixPacketInfo.java Log Message: Adding crypto stuff. IT HAS NOT BEEN TESTED YET Also no changes have been made the the mixlet code to make it use this. Index: MixEncryptedHeaderPart.java =================================================================== RCS file: /cvsroot/mixlet/mixlet/src/MixEncryptedHeaderPart.java,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** MixEncryptedHeaderPart.java 18 Dec 2002 16:07:10 -0000 1.1.1.1 --- MixEncryptedHeaderPart.java 19 Dec 2002 21:48:39 -0000 1.2 *************** *** 11,16 **** import java.security.*; ! import javax.crypto.*; ! import javax.crypto.spec.*; import java.security.spec.*; import java.util.*; --- 11,16 ---- import java.security.*; ! //import javax.crypto.*; ! //import javax.crypto.spec.*; import java.security.spec.*; import java.util.*; Index: MixPacketInfo.java =================================================================== RCS file: /cvsroot/mixlet/mixlet/src/MixPacketInfo.java,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** MixPacketInfo.java 19 Dec 2002 14:26:10 -0000 1.2 --- MixPacketInfo.java 19 Dec 2002 21:48:39 -0000 1.3 *************** *** 11,16 **** import java.security.*; ! import javax.crypto.*; ! import javax.crypto.spec.*; import java.security.spec.*; --- 11,17 ---- import java.security.*; ! //import javax.crypto.*; ! //import javax.crypto.spec.*; ! import xjava.security.*; import java.security.spec.*; |
From: <bfo...@us...> - 2002-12-19 21:43:32
|
Update of /cvsroot/mixlet/mixlet/src/cryptix/util In directory sc8-pr-cvs1:/tmp/cvs-serv6824/util Log Message: Directory /cvsroot/mixlet/mixlet/src/cryptix/util added to the repository |
From: <bfo...@us...> - 2002-12-19 21:43:32
|
Update of /cvsroot/mixlet/mixlet/src/cryptix/provider In directory sc8-pr-cvs1:/tmp/cvs-serv6824/provider Log Message: Directory /cvsroot/mixlet/mixlet/src/cryptix/provider added to the repository |
From: <bfo...@us...> - 2002-12-19 21:39:57
|
Update of /cvsroot/mixlet/mixlet/src/cryptix In directory sc8-pr-cvs1:/tmp/cvs-serv4828/cryptix Log Message: Directory /cvsroot/mixlet/mixlet/src/cryptix added to the repository |
From: <we...@us...> - 2002-12-19 21:00:48
|
Update of /cvsroot/mixlet/mixlet/src In directory sc8-pr-cvs1:/tmp/cvs-serv15458 Modified Files: test.html Log Message: Added h1 tag (actually checking cvs commit mail setup) Index: test.html =================================================================== RCS file: /cvsroot/mixlet/mixlet/src/test.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** test.html 19 Dec 2002 20:34:11 -0000 1.2 --- test.html 19 Dec 2002 21:00:44 -0000 1.3 *************** *** 4,7 **** --- 4,8 ---- </HEAD> <BODY> + <H1>Mixlet Test</H1> <APPLET height=525 width=750 CODE="MixMaster.class" ARCHIVE="MixMaster.jar"> <PARAM NAME="mailserver" VALUE="newyork"> |
From: Len S. <ra...@ab...> - 2002-12-09 17:38:35
|
On Fri, 6 Dec 2002, Bryan L. Fordham wrote: > Here's my idea on how to proceed with mixlet. Let me know of any > suggestions or problems with this. > > 0.5 - Where I think we stand now > 0.6 - Move some things around (basically create some pacakges) and write > an ant script to compile everything > 0.7 - All crypto should be internal (ie using classes from cryptix or > whatever) > 0.8 - Move off of using port 25 to send mail > 0.9 - Config and cleanup. Someone deploying mixlet should be able to > access a simple interface to configure it. > > From there proceed with bug fixes to 1.0 > > For 0.8 I think we could easily supply 3 ways to send the message: a > jsp, a php page, and a cgi. All could basically take the message and > pipe it to the local mix instance. > > On .9 milestone: One thing we may want to add into this is using > user-supplied keys (and stats?). I say maybe because I don't know what > all is involved in getting an applet to read local files. I would shift all those numbers down by one, and include in there an explicit milestone release for handling the key file problem. (There are a number of possible solutions, from user-supplied keys to a third-party remailer keyring CA. None of them are nice.) > I'd like to see all the mix stuff in a seperate library; Len wants this > release quickly (I think). So I'd like to make the move to a library a > goal for version 2. That would be the time to add typeIII support, I think. > > Anyway, that's how I see it. Looks good! |
From: Bryan L. F. <bfo...@so...> - 2002-12-06 15:23:07
|
Here's my idea on how to proceed with mixlet. Let me know of any suggestions or problems with this. 0.5 - Where I think we stand now 0.6 - Move some things around (basically create some pacakges) and write an ant script to compile everything 0.7 - All crypto should be internal (ie using classes from cryptix or whatever) 0.8 - Move off of using port 25 to send mail 0.9 - Config and cleanup. Someone deploying mixlet should be able to access a simple interface to configure it. From there proceed with bug fixes to 1.0 For 0.8 I think we could easily supply 3 ways to send the message: a jsp, a php page, and a cgi. All could basically take the message and pipe it to the local mix instance. On .9 milestone: One thing we may want to add into this is using user-supplied keys (and stats?). I say maybe because I don't know what all is involved in getting an applet to read local files. I'd like to see all the mix stuff in a seperate library; Len wants this release quickly (I think). So I'd like to make the move to a library a goal for version 2. That would be the time to add typeIII support, I think. Anyway, that's how I see it. --B |