Re: Lack of PGP signatures
At 02:07 PM 7/3/96 -0700, Bill Frantz wrote:
At 12:15 PM 7/3/96 -0700, Bill Frantz wrote:
On my Mac I just entered this answer, cut it to the clipboard, launched PGP, clearsigned it, and pasted the result back into the Eudora window for the new mail.
But of course the signature doesn't check. (I suspect Eudora line wrapping.)
Yep. Been there, done that. Line wrap problems are the bain of PGP sigs. This is the reason that most PGP shells will force a line wrap before generating the signature. The only way around it is to turn off all line wrapping or have a utility do it for you before signing it. I am wondering why there is not a signing option that ignores all non-printing characters. Might fix some of these problems... (Can anyone think of a reason this would be a "Bad Thing(tm)"?) --- |"Computers are Voodoo -- You just have to know where to stick the pins."| |"The moral PGP Diffie taught Zimmermann unites all| Disclaimer: | | mankind free in one-key-steganography-privacy!" | Ignore the man | |`finger -l alano@teleport.com` for PGP 2.6.2 key | behind the keyboard.| | http://www.teleport.com/~alano/ | alano@teleport.com |
On Wed, 3 Jul 1996, Alan Olsen wrote:
I am wondering why there is not a signing option that ignores all non-printing characters. Might fix some of these problems... (Can anyone think of a reason this would be a "Bad Thing(tm)"?)
IANACE, but off the top of my head I'd say clear signing binaries. Petro, Christopher C. petro@suba.com <prefered for any non-list stuff> snow@crash.suba.com
-----BEGIN PGP SIGNED MESSAGE----- On Wed, 3 Jul 1996, snow wrote:
On Wed, 3 Jul 1996, Alan Olsen wrote:
I am wondering why there is not a signing option that ignores all non-printing characters. Might fix some of these problems... (Can anyone think of a reason this would be a "Bad Thing(tm)"?)
IANACE, but off the top of my head I'd say clear signing binaries.
It is not possible to clear-sign binaries with PGP. The point of clear-signing is to have signed text that is readable to people who don't have the software necessary to process the text. It would make sense to clearsign a file that is base64'ed or uuencoded, which wouldn't alter the contents of the file. I can't see how such an option would be harmful, except that it might lose some characters that are important to the context of the message. - -- Mark =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= markm@voicenet.com | finger -l for PGP key 0xe3bf2169 http://www.voicenet.com/~markm/ | d61734f2800486ae6f79bfeb70f95348 "Freedom is the freedom to say that two plus two make four. If that is granted, all else follows." --George Orwell, _1984_ -----BEGIN PGP SIGNATURE----- Version: 2.6.3 Charset: noconv iQCVAwUBMdwIoLZc+sv5siulAQHVegQAqeyjQY9SmQ4mM1/ezBDeI9MLa3EZ8620 JXrbxYCt74zUFzqC8GxylUE9cowdZmDrQ2NbYepWbekoY/cmSE3lxJPd1VW36Lbo NY3c1iNswvUiAsfXPUA+tBide/aZCk/vniHXFwLBPJi+gRTjktpbIUNixoxW3B5z xJSFusVl8Lg= =QUGA -----END PGP SIGNATURE-----
I am wondering why there is not a signing option that ignores all non-printing characters. Might fix some of these problems... (Can anyone think of a reason this would be a "Bad Thing(tm)"?)
Moving spaces could change meaning on a legal doc. A nonsense example is the alt.folklore.urbane "cow orker" tag... -- A host is a host from coast to coast.................wb8foz@nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433
participants (4)
-
Alan Olsen -
David Lesher -
Mark M. -
snow