Re: [pe-users] PGPEnvelope not using -t when encrypting?
Brought to you by:
ftobin
|
From: L. S. <ra...@qu...> - 2000-05-01 00:23:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 30 Apr 2000, Frank Tobin wrote: > -----BEGIN PGPENVELOPE PROCESSED MESSAGE----- > > L. Sassaman, at 03:25 -0700 on Sun, 30 Apr 2000, wrote: > > > Don't bother. I have fixed it (was a problem in GnuPG::Interface), and > > attached the patch and sig. > > First, it's not good to change GnuPG::Interface so that it doesn't > directly conform to GnuPG, unless it is fixing to to by by the OpenPGP > spec, the goal of GnuPG. GnuPG::Interface is meant to be a strict, > hardcore, no flirts layer over GnuPG, no compatibility issues discussed. > Pathches for compatibility should be put into the products that use it. > BTW, if you were to patch GnuPG, the cleanest way to do so would have been > to edit the default for textmode in GnuPG::Options, but thanks for trying > :) Well, I would think that you would want to be able to call text or binary modes from GnuPG::Interface. It just seems to make more sense to put it in there... > Next, I'm not entirely sure that the --textmode option should be passed > for pgpenvelope. If zip a text file, and then send it to a windows > machine, and then unzip it, no carriage returns 'magically appear'. So I > don't know how I should approach the issue; preferabbly I'd like to know > what 'should' be happening specwise. When specificallly are you having > problems with an absense carriage returns? It is necessary for OpenPGP. Check 7.1 in the current draft. If you don't give it the --textmode option, it does not know that this is a canonical text document, and treats it as a binary doc. I think that 5.2.1 discusses this as well. __ L. Sassaman System Administrator | Technology Consultant | "To hold a pen is to be at war." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Voltaire -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5DMx0PYrxsgmsCmoRAsqDAKDSDrp6DbqU+l5w598ds3PdnYcwaQCcDz2E rY7WxCXbVhxFi6dsvdKkiWo= =8M4v -----END PGP SIGNATURE----- |