From: jason carr Area: Public Key Encryption To: Brian Giroux 4 Jan 95 08:10:34 Subject: KEY REVOKE UpdReq -----BEGIN PGP SIGNED MESSAGE----- Brian Giroux wrote in a message to Jason Carr: JC>Either the person has to have the ability to follow directions closely BG> That's exactly why I messed up. I didn't follow directions That's why almost =everybody= messes up at first. It takes more attention than we're used to giving to new aps. BG> There were no explanations as to why the step was BG> important, so I just skipped the stuff that looked to weird BG> to me. Heh heh. Maybe that's not the =best= method. :) JC>(ie "Extract a copy of your key =first=") or be able to think ahead. BG> Yeah. I did that back in November to post my public key in BG> the PKEY_DROP echo. Am I saved? Uh, yeah (I think). Never considered it before. If the extraction only acts on your public key ring (not the secret) then you should be able to re-add it. Let's try. In the next msg I'll quote your key back to you, and you can try to re-add it. If it works, and if you've distributed a now-revoked key to a friend (who has =not= applied the revocation) then maybe we've been overlooking an easy solution. :\ Or maybe =I'm= missing some complication. JC>this show weaknesses in the chain: someone who would accidentally and >irretrievably revoke their own key might also make other errors in BG> No, no, no. I never make mistakes! ;) That's ok. I make enough mistakes that I can afford to lend you a couple. jason ... I seen you do the dog, I seen you gettin down. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP_ECHO: CypherEcho to the gods... iQCVAwUBLwrJz0jhGzlN9lCZAQHvkQP9HGeBc9aercX2GJ+esbq5e/fUrBLMp92K PHS50OUROcS5XrytWkwo0GSRpIRBFZ1i2YwGOlPVaK+QtmsPA/KKtGMYqtNrUHZU 8/jgSt3uvaluRmmvrZw3mmwYodGK63JkqBvbHAy95bBKMiHrCXKkmfgLWWt6Akux UnlJH4ZDQyI= =RxWa -----END PGP SIGNATURE----- ... Key fingerprint = 60 97 B2 AE 7D 90 11 2F 05 1C 35 98 E9 B9 83 61 201434369420143436942014343694201434369420143436942014343694718 From: jason carr Area: Public Key Encryption To: Brian Giroux 4 Jan 95 08:21:34 Subject: KEY REVOKE UpdReq -----BEGIN PGP SIGNED MESSAGE----- Brian Giroux wrote in a message to Rich Veraa: BG> Do you mean the ASCII file like this: BG> ~-----BEGIN PGP PUBLIC KEY BLOCK----- BG> ~Version: 2.6a Yes. Before I saw this msg I went back into PKEY_DROP but it'd scrolled off. :( BG> (I just added the "~" to prevent anyone from adding a bad BG> key to their keyring) Bad? Is this the original or the revocation? If it's the original it's good, and fine, and bueno, and wonderful, exciting, shiny, etc. Just delete the revocation from your ring and add in this file. All will be well, Grasshopper. BG> Anyway, this is the file that I created on November 7 for BG> the purpose of posting it to the PKEY_DROP echo. Can I BG> just add this key to my keyring to effectively unrevoke the BG> key? DELete the revocation first (and save it to a file!). jason ... ------+--+ TAGLINE MEASURING TAPE +--+-------- -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP_ECHO: CypherEcho to the gods... iQCVAwUBLwrL1kjhGzlN9lCZAQEVHwP/Wz9RL3u3ZfmxNE3CqCj+K3FpMaO1rUWg TNF/1a35TqgO05GEtwsN9d128T/fyG4N8Ai4lN9c4sSpE+j2JZPY9birW5oSEWMI KIfcITL3Se400SJZ3UUlnXc3cQUPbfNNGXsrbva+ryh5hg3shJWhHhmCNn7H2N9i 2tGvhEPhdc8= =7PTq -----END PGP SIGNATURE----- ... Key fingerprint = 60 97 B2 AE 7D 90 11 2F 05 1C 35 98 E9 B9 83 61 201434369420143436942014343694201434369420143436942014343694718 From: Mark Drew Area: Public Key Encryption To: Todd Jacobs 4 Jan 95 12:31:00 Subject: RE: PROBLEM UpdReq -----BEGIN PGP SIGNED MESSAGE----- -=> Quoting Todd Jacobs to Mark Drew <=- TJ> Most likely a hardware problem. Don't say that :-) TJ> Or possibly a memory conflict. I can live with that one. Thanks for the input -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBLwrjxJTeAMV8DT+pAQEpCgP+KeDXI7bVGY+is1bL11yfDn9TjNGa2CaR vuYAAPPV1zV5l6Y6zsmb26xBhjOc0YKRqiAnG6LFf2tVqoCxtRIDte0Lqb+qOp9t Box6tNYwHDjiCKdcdCUe0QKfH0SEdtzoMjDf++fBTtEWYTli4cYXa0sczkUmGLnr 6d0mPAMRrHg= =44tK -----END PGP SIGNATURE----- ... I don't think I can face another year of annual events. ___ Blue Wave/QWK v2.12 201434369420143436942014343694201434369420143436942014343694718 From: Mark Drew Area: Public Key Encryption To: Jason Carr 4 Jan 95 12:31:00 Subject: Re: Problem UpdReq -----BEGIN PGP SIGNED MESSAGE----- -=> Quoting Jason Carr to Mark Drew <=- JC> Is drive A: mentioned in your PATH statement in your JC> AUTOEXEC.BAT? No, it's not. But thanks for the help. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBLwrkOZTeAMV8DT+pAQFaBAP+IEWNrLeS4PsVYZtKwXg1D/ZXFVrjLEo5 zX5aSVTfjIp9PuXScI/F1VlN0FJjCvMXGcitAXBMr4umYzTp98IBPlLkUwYb2WFc 33EZVH+41OQBoWeSKe5nOuYXD+QT6g0Ws4C1e6O9d4Uz83IpcjCVrMvs5Lt6uByE OJoUgxg0FVE= =8dYK -----END PGP SIGNATURE----- ... "N" could be a vowel if enough people just believed in it. ___ Blue Wave/QWK v2.12 201434369420143436942014343694201434369420143436942014343694718 From: Scott Mills Area: Public Key Encryption To: Christopher Baker 4 Jan 95 14:49:10 Subject: January meeting with Zimmermann's prosecutorUpdReq -----BEGIN PGP SIGNED MESSAGE----- Monday January 02 1995, prz@acm.org writes to All: p> * Forwarded by: Christopher Baker @ 1:374/14 p> * Message text was not edited! p> -+---BEGIN PGP SIGNED MESSAGE-+--- p> Phil Zimmermann and his defense team are heartened by the substantial p> outpouring of support that has been demonstrated through numerous postings p> in this and other news groups. As we approach a crucial meeting with the Do you get a good sig on this? I'm getting a bad sig warning and was wondering if it got mangled after you crossposted or before. Scott Her sweater was so tight the men could hardly breathe. Scott Mills 1024/26CD5D03 For my PGP key freq PGPKEY sm@f119.n265.z1.fidonet.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBLwr8LyP6qSQmzV0DAQGi3AQAuXDXPy0PYi7nmYvmoDSczecp4UY7Bylm l3xMqH618zoeEEHYLQq9U4mE11csikWnMU9qk4aOdvm98tyQmK1DZ2R4ZyyYgizX PkIZ5BWexWkKCgJB2SCZMr3Q/ScztxFN4Bp0cQAIM42FxmC/wNEbc4HUx5cRNn9o Gjsn4jJ9uz0= =/dE5 -----END PGP SIGNATURE----- --- 201434369420143436942014343694201434369420143436942014343694718 From: Ian Hebert Area: Public Key Encryption To: Prz@acm.org 4 Jan 95 09:51:10 Subject: January meeting with Zimm UpdReq PP> The following is a message from my lawyer, Phil Dubois. He posted it PP> to alt.security.pgp, and I thought I should post it here as well. The PP> message is signed with his key. PP> --Philip Zimmermann Don't know if anyone else bothered to check this out, but I get a "bad signature" message when I attempted to verify the signature. Notified Phil Dubois already, but have had no answer. Ian Hebert London, Ontario, Canada RIME: HOMEBASE (5508) Fido: 1:2401/114 Internet: ian.hebert@homebase.com PGP Key: 1024 / 077A2F7F 1993/02/11 PGP Key Fingerprint: A2 15 DE 22 DA FE D4 DC 0F 17 43 24 1F F2 1E 7B * RM 1.3 02664 * Frustrate the NSA, CIA & FBI--Use Pretty Good Privacy (PGP)! 201434369420143436942014343694201434369420143436942014343694718 From: Bill Lambdin Area: Public Key Encryption To: Christopher Baker 5 Jan 95 00:02:10 Subject: Re: my public key UpdReq CHRISTOPHER BAKER To BILL LAMBDIN about Re: my public key on 01-02-95 CB> please post keys only in the PKEY_DROP Echo. OK. Will cooperate in the future. Bill 9CCD47F3C765CA33 bill.lambdin@woodybbs.com C77D698B260CF808 <-PGP fingerprint codes --- * CMPQwk 1.4 #1255 * PLASTIQUE-B activates Sep 20 - Dec 31 201434369420143436942014343694201434369420143436942014343694718 From: Aaron Goldblatt Area: Public Key Encryption To: Jeff Trowbridge 4 Jan 95 21:06:28 Subject: pgp problems UpdReq -----BEGIN PGP SIGNED MESSAGE----- JT>> response, save it, back to Ppoint, open the editor again, but when I run JT>> pgp -sat response.asc I get a completly encrypted message. JT>> Does anyone know why it does this? It's likely that your message text file contains ^a kludge lines, or high-ASCII characters. PGP sees these and assumes a binary file, even if you specify plaintext. Since you specified ASCII armouring, it did ... the entire thing, rendering the message useless ... The only way around this is to be sure that your message doesn't have high ASCII in it. D'Artagnon ... Climb on the back with me, little girl, for a magic carpet ride! - --- GoldED v2.50.B1016+/1111 -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: 43 6C 69 70 70 65 72 20 73 75 63 6B 73 21 iQCVAwUBLws4pr8aRv3HpI1RAQFhNQP/RgIl2WLRDBln0v1gNll1dxN4oe2odQ5R Vxsg2mYZgGi2q95eHN4BuxuP4LVy8QBadxMYyHuazdaYR+Y0MR1F+3i/dfK9J345 8If4LaeBcBE+1OVOIj+3LnTaaVorPWl+o3AtjYItFwNXqNgkav+9uUoJyjuf4UO5 W0/LaW+jZjA= =CvyO -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: SYSOP Area: Public Key Encryption To: All 30 Dec 94 22:24:00 Subject: PGP UpdReq Hello! I have been carrying the public key echo for a while, and was wondering if there is a PGP shell to allow for entering messages online with Searchlight BBS. Just curious! -==- 201434369420143436942014343694201434369420143436942014343694718 From: John Goerzen Area: Public Key Encryption To: TODD JACOBS 3 Jan 95 22:57:06 Subject: Can I Freq Pgp? UpdReq TV> 2.6.2 fixes a lot of bugs, and is fully legal. 'nuff said. You can FREQ TV> here with the magic name of PGP (or try PGP262.ZIP if that fails). Should be added here that 2.6.2 is fully legal only within the US. It is illegal to export it. International users need PGP 2.xx UI (it will always have UI after it). BBS operators can be indicted on criminal charges if somebody from outside the US downloads or FREQs PGP. -- John Goerzen, SysOp: Communications Complete BBS * RM 1.3 * Poker Face: The face that launched a thousand chips. 201434369420143436942014343694201434369420143436942014343694718