Distribution of Secure Drive
-----BEGIN PGP SIGNED MESSAGE----- On Nov 30, I sent a private msg to Eric Hughes asking him to put Mike Ingle's Secure Drive program for MSDOS SECDRV10.ZIP 68155 11-19-93 Secure Drive 1.0 with SRC. On the Soda.Berkeley FTP site and to advise me of its location. I have not received any response at all. I'm on a UUCP system, so I have to do FTP requests via an E-mail server, which is cumbersome if one has to "fish around" for a file one doesn't know the exact directory & filename for. I'm aware that Mike said he hadn't submitted Secure Drive to the FTP site because of "export concerns." But since this site is already distributing PGP, I wouldn't think this a "concern" to the site administration. So I'm asking any public-spirited Cypherpunk (perhaps even an anonymous one) to place Secure Drive on an FTP site or a site with an E-mail file server and to post the location of the file either here or to me privately. -----BEGIN PGP SIGNATURE----- Version: 2.3a iQCVAgUBLQg3Zt4nNf3ah8DHAQHWPwP7Bhr/FkuqS3FqkOszCdB97+P6WtKJPsYR d6VshdtFDm59JKsTcUk1V2wY6//5u+BhpFowgJ0qsGR/pl8Bzcl8upTn+RC2IBKH 07oxyJIlciiqYJ+ghlqnMZiPq/ZZ3Z/jHGTlOW1cAP2jHgT2Ok5kPhrr4mGYlAGO h1FfB8AJsDM= =tUFI -----END PGP SIGNATURE----- -- edgar@spectrx.saigon.com (Edgar W. Swank) SPECTROX SYSTEMS +1.408.252.1005 Cupertino, Ca
In cypherpunks, Edgar W. Swank writes: ...
On Nov 30, I sent a private msg to Eric Hughes asking him to put Mike Ingle's Secure Drive program for MSDOS
SECDRV10.ZIP 68155 11-19-93 Secure Drive 1.0 with SRC.
On the Soda.Berkeley FTP site and to advise me of its location. I have not received any response at all. ...
I'm aware that Mike said he hadn't submitted Secure Drive to the FTP site because of "export concerns." But since this site is already distributing PGP, I wouldn't think this a "concern" to the site administration.
So I'm asking any public-spirited Cypherpunk (perhaps even an anonymous one) to place Secure Drive on an FTP site or a site with an E-mail file server and to post the location of the file either here or to me privately.
Please, please don't do this without checking with the author of the package first. He went out of his way to say that he doesn't want to a make it available for ftp because he doesn't want to deal with potential export problems. So respect his wishes; it's his work, after all. I'm the process of arranging the release of my own Unix crypto file system, and am myself concerned about the export issues (as is my employer). Messages like this one don't exactly give me a warm fuzzy feeling about people violating their agreements to not export the code or otherwise creating future headaches on my behalf. If you think that an author of cryptographic software is immune from export hassles just because it was someone else who exported it, ask Phil Zimmermann... -matt
Matt Blaze writes:
In cypherpunks, Edgar W. Swank writes: ...
So I'm asking any public-spirited Cypherpunk (perhaps even an anonymous one) to place Secure Drive on an FTP site or a site
Please, please don't do this without checking with the author of the package first. He went out of his way to say that he doesn't
...
Messages like this one don't exactly give me a warm fuzzy feeling about people violating their agreements to not export the code or otherwise creating future headaches on my behalf.
Thank you for saying this. I would like to emphatically second it. People are going to quit writing code if this sort of thing starts happening. If you want code exported, write it yourself and export it. Then it's your ass on the line. -- Will
...
I'm the process of arranging the release of my own Unix crypto file system, and am myself concerned about the export issues (as is my employer). Messages like this one don't exactly give me a warm fuzzy feeling about people violating their agreements to not export the code or otherwise creating future headaches on my behalf.
If you think that an author of cryptographic software is immune from export hassles just because it was someone else who exported it, ask Phil Zimmermann...
-matt
I think someone else brought this up: Write the whole skeleton with the proper crypto hooks and then distribute it without the crypto library. You could replace it with xor, or a crc, or something. The crypto library could be distributed more carefully. After all, with pgp etc. source, it isn't the crypto that's hard, it's the OS interface code. I'd love to have such a thing for Linux BTW... sdw -- Stephen D. Williams Local Internet Gateway Co.; SDW Systems 513 496-5223APager LIG dev./sales Internet: sdw@lig.net CIS 76244.210@compuserve.com OO R&D Source Dist. By Horse: 2464 Rosina Dr., Miamisburg, OH 45342-6430 GNU Support ICBM: 39 34N 85 15W I love it when a plan comes together
participants (4)
-
edgar＠spectrx.saigon.com -
Matt Blaze -
sdw＠meaddata.com -
W. Kinney