From: Christopher Baker Area: Public Key Encryption To: All 24 Oct 94 23:48:38 Subject: PGP 2.6.2 Official M.I.T. release UpdReq -----BEGIN PGP SIGNED MESSAGE----- Pretty Good Privacy 2.6.2 has been released by M.I.T. for MSDOS and source. PGP executables and source MAY NOT be exported outside the U.S. [except to Canada] UNLESS you obtain a valid ITAR export license. Exporting cryptography systems outside the U.S. is a FEDERAL CRIME unless you have a license. the following were hatched into PUBKEYZ1 [for Zone 1 ONLY!]: PGP262.ZIP PGP for DOS fixes bugs and enhances ops. [PGP] [282K] PGP262S.ZIP PGP 2.6.2 source code for porting. [PGPSRC] [658K] the following hatched into PUBKEYS [not ITAR restricted]: PGP262DC.ZIP DOCS ONLY archive from M.I.T [included in above]. [PGPDOC] the official OS/2 version will be available shortly and will be hatched into PUBKEYZ1 when received. anytime except 0100-0130 ET and Zone 1 ZMH at 1200-9600+ HST/V32 for FidoNet listed systems [and their legal points] only. Download for first-time callers - 407-383-1372 for Zone 1 Users only. all PUBKEYZ1 and PUBKEYS distribution links please poll. TTFN. Chris -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP 2.6.2 is LEGAL in Zone 1! So USE it! [grin] iQCVAwUBLqyAHcsQPBL4miT5AQGhZgQAoQZr1slyoTdNhKc1a9ekQs3cCBeHIZ1i DHEYVtDXROsypzUlvVMv1dHLixeCbh/pn+ll7Mjbl1kU3/IjFy+Ky+JrK27SaoeN TzyhCLV4UxciWgkctXFtek8WrPH25M66sWpJWjKGOZ3QLmVZq0nmZSi0WAgql594 gDPoKjNJR0A= =sStv -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: Christopher Baker Area: Public Key Encryption To: All 25 Oct 94 00:02:46 Subject: PGP 2.6.2 update note UpdReq -----BEGIN PGP SIGNED MESSAGE----- somewhere along the line [it doesn't say in the CHANGES.DOC] the VERBOSE diagnostic command in CONFIG.TXT changed from =On to =2 or =0. Verbose=2 means verbose diagnostics will be put on your screen even thru GenMsg [and ostensibly other interface utils]. this can be a trifle disconcerting to neophytes so if you have the Verbose command activated in your CONFIG.TXT as Verbose=On you need to change it to one of the numerical values or PGP will quit with an error msg about the line that command appears on needing a numberical value. Verbose=2 gives all the intermediate steps PGP is performing. Verbose=0 keeps it quiet. this is the mode i recommend unless you need to debug something going wrong. be sure to edit your own CONFIG.TXT to use one of those numbers on the Verbose command [if you don't have it commented out]. otherwise, it's functioning normally in DOS. TTFN. Chris -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP 2.6.2 is LEGAL in Zone 1! So USE it! [grin] iQCVAwUBLqyDbMsQPBL4miT5AQGVXgP+I7EYzTES51Ew0eV3Cz/kfSxn5C7BQuFx Kmj43plrNq0iSSAMDRwr1kliUqnOEwnzZp7HOApRa7v5PR7f+rKfU+M7akNR860g C/QN09SY6WefwMw2O2cZ2MrTn0Wh2BucITL5dxULJa4WOdH6qz2VoXKROyXNNcKe kbCpdVT3VOQ= =8Ny9 -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: Michael Burhans Area: Public Key Encryption To: Christopher Baker 19 Oct 94 15:06:00 Subject: Pgp-related filename conv UpdReq Quoting CHRISTOPHER BAKER to ALL concerning PGP-RELATED FILENAME CONV: CB>Version: 2.61 CB>Comment: PGP 2.6.1 is LEGAL in Zone 1! So USE it! [grin] How does one add a comment like this to their key? Michael R. Burhans Message written at 3:05pm, on Wednesday, October 19, 1994. * Apex v4 * Support the Electronic Freedom Foundation! * michael.burhans@wolverine.com <*> Finger for PGP Public Key * SLMR 2.1 * * SLMR 2.1 * 201434369420143436942014343694201434369420143436942014343694718 From: Alan Pugh Area: Public Key Encryption To: All 21 Oct 94 12:17:22 Subject: FBI & Encryption UpdReq -----BEGIN PGP SIGNED MESSAGE----- ==anything above this line is bogus= =snipped from _telecom digest_ = TELECOM Digest Thu, 20 Oct 94 16:22:00 CDT Volume 14 : Issue 403 Inside This Issue: Editor: Patrick A. Townson FCC Q & A on Broadband PCS Auctions (Bob Keller) "The Road to Banning Encryption" (Gordon Jacobson) AT&T 800 Directory Release (Monty Hoyt) Comparison of Missouri Intrastate Rates (Will Martin) TELECOM Digest is an electronic journal devoted mostly but not exclusively to telecommunications topics. It is circulated anywhere there is email, in addition to various telecom forums on a variety of public service systems and networks including Compuserve and America On Line. It is also gatewayed to Usenet where it appears as the moderated newsgroup 'comp.dcom.telecom'. Subscriptions are available at no charge to qualified organizations and individual readers. Write and tell us how you qualify: * telecom-request@eecs.nwu.edu * The Digest is edited, published and compilation-copyrighted by Patrick Townson of Skokie, Illinois USA. You can reach us by postal mail, fax or phone at: 9457-D Niles Center Road Skokie, IL USA 60076 Phone: 708-329-0571 Fax: 708-329-0572 ** Article submission address only: telecom@eecs.nwu.edu ** =snip= Date: Thu, 20 Oct 1994 13:35:37 -0400 From: gaj@portman.com (Gordon Jacobson) Subject: The Road to Banning Encryption Pat - I got this from David Farber. It sure is a telling tale! Let me know what you can do about posting it. [TELECOM Digest Editor's Note: Yes, it is interesting. I thought the readers might enjoy seeing it today. PAT] CyberWire Dispatch // Copyright (c) 1994 // Jacking in from the "Sooner or Later" Port: Washington, DC -- If private encryption schemes interfere with the FBI's ability to wiretap, they could be outlawed, according to recent comments made by the agency's Director Louis Freeh. Freeh told attendees here at the recent conference on Global Cryptography that if the Administration's Escrowed Encryption System, otherwise known as the Clipper Chip, failed to gain acceptance, giving way to private encryption technologies, he would have no choice but to press Congress to pass legislation that provided law enforcement access to *all* encrypted communications. If, after having pushed Digital Telephony through Congress (which hadn't yet happened when Freeh spoke at this conference), all the Bureau ended up with during wiretaps were the scratchy hiss of digital one's and zeros being hurled back and forth, Freeh made it clear that he would seek a congressional mandate to solve the problem. In other words: Roll your own coded communications; go to jail. Freeh's comments, made during a question and answer session at the conference, are the first public statements made by an Administration official hinting at a future governmental policy that could result in the banning of non-governmental, unbreakable encryption methods. Freeh's remarks were first reported on the WELL by MacWorld writer and author Steven Levy. The FBI confirmed those statements to Dispatch. The Administration, however, continues to state that it has no plans to outlaw or place any restrictions on private encryption methods. A White House official said there are "absolutely no plans" on the table to regulate domestic encryption "at the present time." He wouldn't comment, however, as to whether the Administration would back an FBI attempt for such legislation. "Freeh doesn't seem to need a lot of White House support," to get things done, the official said. FBI sources said any moves to approach Congress about regulating private encryption are "so far out there" time wise, that the subject "doesn't merit much ink," as one FBI source put it. "We've got to make sure the telcos rig up their current networks according to the new [digital wiretap] law before we go worrying about private encryption stuff," he said. An FBI spokesman confirmed Freeh's position that the Bureau would aggressively seek to maintain what the spokesman called "law and order objectives." If that meant getting laws passed so that the Bureau's "authorized wiretap activities" couldn't be thwarted by "criminal elements using non-governmental" encryption schemes, "then that's what he [Freeh] would do," the spokesman said. When the Administration went public with its Clipper Chip policy, it stressed that the program would be mandatory. Many civil liberties groups wondered out loud how long it would be before private encryption was banned altogether. The White House, anxious for the public to buy into its one-trick pony the Clipper Chip, said that wouldn't happen. But the Administration hedged its bet. Buried in the background briefing papers of the original Clipper announcement, is a statement that the White House doesn't consider the public's right to use private encryption methods are protected anywhere in the Constitution. Meeks out ... ------------------- Regards, - GAJ Home Page: http://www.seas.upenn.edu/~gaj1/home.html -----BEGIN PGP SIGNATURE----- Version: 2.3a iQCxAgUBLqf2tNQ9obngT6LhAQFYyATeKkDHEb63QAN92v8LUXAX6otMh9i+aDDY P/zzc24l6t/agvpXZQrBZ+EuMAagfT42Wk3LdXFVF8ZHucCozTqAJEpRiNTTE3me WiXx953x8sDt41+jiAJmdUhh4CXUyBCB8kLed22TS8Aa7cZ0v7dkfX9LyWw6c9bm clHEFRvSa2krgxijvCxHusXpP/JIlKQtAfnCAIJTMyyC8tC6 =IjcF -----END PGP SIGNATURE----- ... I drank What? - Socrates 201434369420143436942014343694201434369420143436942014343694718 From: Jim Grubs, W8GRT Area: Public Key Encryption To: Peter Bradie 24 Oct 94 19:38:00 Subject: Pgp signatures UpdReq > -=> Quoting Brian Mcmurry to Joe Eversole <=- > JE> You're the only person I have a key for that you sent this to... Where > do > JE> you find your keys? I usually add most keys I find in the PKEY_DROP > JE> echo... > BM> You're on my keyring. I add most of the ones that come through > BM> PKEY_DROP and cypherpunks. > If I'm out of line, please let me know. If not, then > could you explain > the rationale for accumulating keys from people you do The rationale is that if someone wanted to tamper with your key or create a phony in your name he would have to replace all the copies on everybody's keyring. Sincerely, Jim Grubs, W8GRT 201434369420143436942014343694201434369420143436942014343694718 From: John Schofield Area: Public Key Encryption To: All 24 Oct 94 20:06:54 Subject: PGP version 2.6.2 UpdReq -----BEGIN PGP SIGNED MESSAGE----- The new version of PGP was released today (October 24, 1994) and it is available for FREQ from my system. Magic name PGP will get you PGP262.ZIP, and PGPSRC will get you PGP262S.ZIP. You can FREQ it from: 1:102/903.0 Zoom 14.4k BPS 1:102/904.0 Practical Peripherals 28.8k BPS V.FAST JMS -----BEGIN PGP SIGNATURE----- Version: 2.7 Comment: Call 818-345-8640 voice for info on Keep Out magazine. iQCVAwUBLqx2H2j9fvT+ukJdAQHwpAP/XZ/qDMh8l9Vly2/LtLGYeQT21oWpNyWI chTwSlgChOTX0N5yC/5MJVvEGmOlksQa2+4Xd8GTbskw/0eQmx2YqTeNcuzVoE8B zgengoyRUF8fbdBnhxJwSdJ5zomKdXuDustYz0LZh3DsDCtsADA6cwFs6lGe/BB+ DV5HBuead9s= =19ef -----END PGP SIGNATURE----- **EZ-PGP v1.07 ... "What do you mean you reformatted the cat?" 201434369420143436942014343694201434369420143436942014343694718 From: Christopher Baker Area: Public Key Encryption To: Michael Burhans 25 Oct 94 15:47:54 Subject: Re: Pgp-related filename conv UpdReq -----BEGIN PGP SIGNED MESSAGE----- In a message dated: 19 Oct 94, Michael Burhans was quoted as saying: MB> CB>Comment: PGP 2.6.1 is LEGAL in Zone 1! So USE it! [grin] MB> How does one add a comment like this to their key? put the following line in your PGP file CONFIG.TXT: comment=Whatever your comment is and keep it short to avoid wrapping probs. [grin] TTFN. Chris -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP 2.6.2 is LEGAL in Zone 1! So USE it! [grin] iQCVAwUBLq1g7ssQPBL4miT5AQGlZgP9FhLymO6nwZQkbivaxE5idphsT56QHlR0 00p3ObDU20+L6tE+B3cWwhxafT1cfjkS3tOidCByCyhlfXNaQrltMjRrhcbDPVrC srjdCMj7BqNU7CF5rqIVtL4P9qC8aCQG0hI+OxcecPfjy9xMe1Otxt0i7Ggy5eOa aPA4/drtzc4= =zofR -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: Jeremy Scott Area: Public Key Encryption To: All 25 Oct 94 10:45:04 Subject: cryptography UpdReq ok...whats the big deal here some explain to me what the whole "privicy" thing is about...im interested... > eremy > 201434369420143436942014343694201434369420143436942014343694718