From: Dave Hodgins Area: Public Key Encryption To: Christopher Baker 29 Oct 94 00:26:00 Subject: Public Key UpdReq -----BEGIN PGP SIGNED MESSAGE----- CB> In a message dated: 26 Oct 94, Dave Hodgins was quoted as saying: CB> DH> -----BEGIN PGP PUBLIC KEY BLOCK----- CB> oops. wrong Echo. [grin] CB> please put keys in PKEY_DROP Echo. CB> thanks. CB> TTFN. CB> Chris Thanks for pointing that out to me! I intended to post it in the public key drop echo, and obviously got the wrong conference. I am aware of the difference between the two conferences, and it was an honest mistake. I'll repost my public key in the correct conference. Again, Thanks, Dave Hodgins. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBLrHPEJbACHtihSGlAQGUJgP5AW7aKhCyMe/lgaPazTIFZnvPggTQqIEc pcrXZS27IKAmxDmhlmZ3UoaJUEjAFzOpAa+sPUKOw3OaFQoKDNUwneAB2erpFKL+ 8wVAUAbA4kGxZ6PPcgE2VN/YO25Qg4VGf6qtbyeZT4eBRWB4vzvgJk67VB+bZMnx rab1ERBwdZY= =5cph -----END PGP SIGNATURE----- **EZ-PGP v1.07 --- * RM 1.3 00820 * Internet:Dave.Hodgins@Canrem.com Rime->118 Fido(1:229/15) 201434369420143436942014343694201434369420143436942014343694718 From: Wes Perkhiser Area: Public Key Encryption To: all 25 Oct 94 17:30:16 Subject: hpack UpdReq Looking for a FREQable source for MS-Dos version of HPACK (any version later than 0.78) and/or KEYCVT (to allow the HPACK to use public key encryption). Thanks, Wes 201434369420143436942014343694201434369420143436942014343694718 From: Scott Redd Area: Public Key Encryption To: Jerome Greene 25 Oct 94 20:28:16 Subject: Which PGP version is best? UpdReq Saturday October 15 1994 15:49, Jerome Greene wrote to David McIntyre: JG> Sure you have an internet address it is JG> You could also set it up like JG> this David McIntyre <1:3625/441@fidonet.org> Either way you are JG> identified as being at that address. Just examples in any case. Jerome JG> Greene Unless things have changed, I think the gatekeeper at fidonet.org will not pass encrypted mail to/from the innternet. If anyone else has more information about this please post it to the echo. Scott # Origin: Orifice -- portable [Omaha, NE] (1:285/5.47) * Origin: PODNet <-> FidoNet EchoGate! (93:9600/0.0) SEEN-BY: 107/946 147/1077 152/53 153/9125 259/212 382/7 640/217 3611/19 SEEN-BY: 9600/0 9608/0 201434369420143436942014343694201434369420143436942014343694718 From: Scott Redd Area: Public Key Encryption To: Richard Wallen 25 Oct 94 20:58:18 Subject: Which PGP version is best? UpdReq Sunday October 16 1994 08:45, Richard Wallen wrote to David McIntyre: RW> A good version of pgp running here so far is the 2.61, released shortly RW> after the MIT 2.6.1 release.. an example [imho] regarding your ID, might RW> be: David McIntyre where the latter RW> suggestion should be something personal... maybe even.and.or an aniversary RW> date. I suggest that David include that along with any other user id's he may need. Following is how my key looks: pub 1024/6D3FE9 1994/04/29 Scott H Redd Scott H Redd Scott H Redd Scott Redd <1:285/5.47 FidoNet> Scott H Redd There is a userid for each of my major email addresses, including Fidonet. Also, just for the hell of it, I included my city, state and country. This would come in handy if someone was doing simple string search via an automated keyserver. Now if I could just get those userids sorted by order of most important. Scott # Origin: Orifice -- portable [Omaha, NE] (1:285/5.47) * Origin: PODNet <-> FidoNet EchoGate! (93:9600/0.0) SEEN-BY: 107/946 147/1077 152/53 153/9125 259/212 382/7 640/217 3611/19 SEEN-BY: 9600/0 9608/0 201434369420143436942014343694201434369420143436942014343694718 From: Mike Riddle Area: Public Key Encryption To: Jim Bell 29 Oct 94 09:11:20 Subject: PGP 2.6.2 Official M.I.T. UpdReq In a message to CHRISTOPHER BAKER on Oct 26 94 at 21:51, Jim Bell wrote: JB> Justa moment there. Presumably, the object code is JB> restricted for export due to the fact that it contains a JB> program that can do encryption. However, the source code JB> (by itself) cannot encrypt anything. JB> Is there any reason to believe that source code (or even JB> equations, explanation, etc) can be legitimately JB> restricted? JB> It's not as if I'd be surprised if the government were to JB> take such a foolish position; however I haven't heard that JB> one yet. Notwithstanding the plain language of the ITAR about these matters, Da Guvmint (which always knows best) continues to insist that source code, at least in electronic form, is export-controlled. Bruce Scheirer(sp?) wrote _Applied Cryptography_ and my understanding is that the book could be exported, but not the disk that contained programs listed in the book. Go figure. 201434369420143436942014343694201434369420143436942014343694718 From: Garet Jax Area: Public Key Encryption To: All 28 Oct 94 03:54:00 Subject: CRYPTOGRAMS UpdReq I'd like to receive cryptograms (of the type found published in newspapers and magazines) from anyone who may have old copies laying about. I'm attempting to write a program to solve these and would like a bunch of real samples rather than ones that I could generate myself. Thanks in advance, -Garet 201434369420143436942014343694201434369420143436942014343694718 From: John Schofield Area: Public Key Encryption To: Jim Bell 29 Oct 94 13:21:00 Subject: PGP 2.6.2 Official M.I.T. UpdReq -----BEGIN PGP SIGNED MESSAGE----- --== CB> the following were hatched into PUBKEYZ1 [for Zone 1 ONLY!]: CB> PGP262.ZIP PGP for DOS fixes bugs and enhances ops. [PGP] [282K] CB> PGP262S.ZIP PGP 2.6.2 source code for porting. [PGPSRC] [658K] JB> Justa moment there. Presumably, the object code is restricted for JB> export due to the fact that it contains a program that can do JB> encryption. However, the source code (by itself) cannot encrypt JB> anything. JB> Is there any reason to believe that source code (or even equations, JB> explanation, etc) can be legitimately restricted? Equations, algorithms, and descriptions of source code can not be restricted. Source code and executables are. And in reality, not restricting source code because it "can't do anything" is very nit-picky and silly. If you want to discuss the validity of export restrictions at all, that's a different story. {grin} JB> Also: The government currently approves certain (weak) encryption JB> programs for export. What if somebody slightly modified a version of JB> PGP to include a single line EQUate that sets the maximum number of JB> bits in the key to, say, 40. JB> Exported legally, the number would then simply be changed to 2048 and JB> recompiled, returning the program to full functionality. JB> If the government said, "You can't export a program that can be JB> modified to do good encryption," then the proper answer is that ANY JB> program can be modified to do good encryption, with enough changes. But since the full, unmodified PGP somehow always finds its way out of the country, there is no need for this subterfuge. Also, there's no reason the State Department would approve this modified PGP. There's no ruling that says software using keys smaller than 40 can be exported. All we know is that in some cases, software using keys smaller than 40 has been approved, while just about everything else hasn't. The State Department handles these things on a case-by-case basis. They could easily reject this modified PGP for export. JMS ... "What do you mean you reformatted the cat?" -----BEGIN PGP SIGNATURE----- Version: 2.7 Comment: Call 818-345-8640 voice for info on Keep Out magazine. iQCVAwUBLrKt1Wj9fvT+ukJdAQH44gQAgQam5Drvs7TfOq3qDG8k1yey03PDBIYB 4vxg5e967ZQ5PAORBH1/hABtudNkMFV6qKsOEdvzLNLnT6/2zlLO10Zx3sHEwCRU lx18anCWneRI9CODN/JtNqqmeWStgyEKcGnZLjwsCNe2M6lz1R6ggqYOr19bFqG3 wOa14aEdViw= =5x2z -----END PGP SIGNATURE----- **EZ-PGP v1.07 201434369420143436942014343694201434369420143436942014343694718 From: John Schofield Area: Public Key Encryption To: John Mudge 29 Oct 94 13:21:02 Subject: PGP embedded in .gif's ? UpdReq -----BEGIN PGP SIGNED MESSAGE----- --====-- JM> ====== Anyone have the source file for placing pgp encrypted messages in JM> a .gif for distribution over the net ? JM> With the latest rumblings from the folks at the FBI, it would be nice JM> to have the program NOW and not wait till later. S-TOOLS.ZIP 278491 27-Oct-94 S-Tools for Windows. Version 2.00. Steganography program for Windows. S-Tools (Steganography Tools) brings you the capability of `hiding' files within Windows sound files (.WAV), bitmap (.BMP) and CompuServe GIF files. For BMP's and GIF's you can choose whether you want the graphic image to look identical after a file has been hidden inside, or whether you can put up with some degradation of definition in order to gain other advantages. Files hidden inside WAV's will not sound any different to the human ear than the original file. STEALTH.ZIP 11082 19-Oct-94 Obtained by FTP from: ftp.dsi.unimi.it/pub/security/crypt/PGP/. FROM README FILE: STEALTH HAS NOT YET BEEN TESTED ON MS-DOS, but the only likely problems are with 16-bit integers (you may need to change some occurences of int to long in order to get stealth to work), and you will need to remove the -DUNIX flag from compilations. Hopefully, version 1.1 will be released shortly with full DOS compatibility. Stealth is a simple filter for PGP which strips off all identifying header information to leave only the encrypted data in a format suitable for steganographic use. That is, the data can be hidden in images, audio files, text files, CAD files, and/or any other file type that may contain random data, then sent to another person who can retrieve the data from the file, attach headers, and PGP decrypt it. Stealth is not intended to replace the standardised methods of using encryption (e.g. ASCII-armoured PGP email); in an ideal world we would all be able to send openly encrypted mail or files to each other with no fear of reprisals, however there are often cases when this is not possible. STEGO.ZIP 277654 23-Aug-94 Send encrypted messages and files which are undetectible and REQUIRE NO KEY! Programs and messages are submerged into a graphic file (usually a B/W TIF file). Once the object has been hidden the TIF appears unchanged when viewed with a TIF viewer. This technique can support other encryption technologies. But instead of having a file which draws attention to itself, you have a normal graphic. In this case, a picture IS worth 1000 words. WNS210.ZIP 84102 01-Jun-94 White Noise Storm: Data Encryption/Steganography package. You can use this to hide files in PCX pictures so nobody will see them. All these are available for FREQ from the Sprawl at 1:102/903 (14.4) 1:102/904 (28.8) All systems can request. JMS ... "Happiness is a warm puppy," said the anaconda. -----BEGIN PGP SIGNATURE----- Version: 2.7 Comment: Call 818-345-8640 voice for info on Keep Out magazine. iQCVAwUBLrKuXGj9fvT+ukJdAQHCDAQAjA90untHcopfS2aeHnSjAcKfKO6xfyxP olfzTbvFgq9qmdNcurpgbMv9q+DhUtyQOKCbG1ozXtlmdl0vXMwMtVJepyAUI6Ut 6ZIu4d2ZDFddYmDaB5C9jg5PiMj5qNEsjczn/Aks8YBCK4FBIgmRDdKhjODm9Rfj m6iYLfBS1LU= =k9fg -----END PGP SIGNATURE----- **EZ-PGP v1.07 201434369420143436942014343694201434369420143436942014343694718 From: Shawn McMahon Area: Public Key Encryption To: Wes Perkhiser 30 Oct 94 16:21:30 Subject: hpack UpdReq Despite the stern warnings of the tribal elders, Wes Perkhiser said this to all: WP> Looking for a FREQable source for MS-Dos version of HPACK (any WP> version later than 0.78) and/or KEYCVT (to allow the HPACK to use WP> public key encryption). I just recently uploaded the DOS and OS/2 versions of .79 (which is the latest, although the author does have some modifications in mind if he ever finds the time to incorporate them) to 1:396/1. I do not know if they're currently available for FREQ, but the filenames were: HPACK79D.ZIP (DOS version.) HPACK79O.ZIP (OS/2 version.) Additionally, I sent the OS/2 version to 1:109/347. It's shown up in his filelist since then. I also have the source code, and a Macintosh compile. It's compressed with whatever produces .CPT files, however, so I haven't checked it for CRCs or anything. KEYCVT was included in the OS/2 archive; I don't know if it was in the DOS, it's off on a floppy somewhere. 201434369420143436942014343694201434369420143436942014343694718