Frustration (forgive a FAQ please)
Sun, 26 Sep 1999 06:37:17 +0000
Content-Type: text/plain; charset=us-ascii
On Sun, Sep 26, 1999 at 12:00:17AM -0600, Jason Gunthorpe wrote:
> On Sun, 26 Sep 1999, Lazarus Long wrote:
> > Could someone please tell me how I can communicate with this particular
> > privacy advocate who insists upon using pgp2 out of distrust of "newer"
> > versions? Not only am I unable to get mutt to do what I want (after
> The precise set of options I use for generating encrypted messages that
> PGP2 will read is:
> gpg --no-options --batch --load-extension rsa --no-default-keyring
> --keyring [foo] --output - --quiet --always-trust --armor -r 0x[to
> keyfingerprint] --rfc1991 --load-extension idea --cipher-algo
> idea --encrypt foo.txt > output
Using that verbatim, substituting only for "foo.txt" and "output" and
of course the two -r fields, I get the following:
$ pgp outputfile
Pretty Good Privacy(tm) 2.6.3ia - 1996-03-04
Current time: 1999/09/26 06:19 GMT
File is encrypted. Secret key is required to read it.
Unsupported packet format - you need a newer version of PGP for this file.
Which shows me that the result is NOT readable by pgp2. Please try this
on your own end Jason and you'll see what I mean. I am quite frustrated
that nothing is working here.
BTW, I also used the "--output - --quiet" you used, even though I wasn't
sure the single-dash wasn't a typo. Oh, one other obvious substitution
I made was changing "[foo]" to "~/.gnupg/pubring.gpg" of course.
Please, someone, explain to me why I can not write this pgp2 user,
no matter what I try.
> It is critical that you ecrypt a file given on the command line not using
> a pipe. GPG uses a different packet format that PGP 2.x will not read.
I did so, with the results (failure) you saw above.
> --keyring ~/.pgp/pubring.pgp --output - --quiet --always-trust --armor -r
You are using ancient-style keys then? What about those of us who use
gpg-default style keys? (I dont use a .pgp/* or any *.pgp).
> gpg: 35261E21: no info to calculate a trust probability
Yes, I got similar to this myself, even though specifying always-trust,
which surprised me.
> gpg: RSA keys are deprecated; please consider creating a new key and use
> this key in the future
I got this too.
> gpg: this cipher algorithm is depreciated; please use a more standard one!
Bug report, typo. s/depreciated/deprecated/ (Werner?) I got this as well.
Note that pgp2 still says I need a "newer version" to read the resultant
Please encrypt all mail whenever possible. The following Public Keys
for Lazarus Long <firstname.lastname@example.org> are available upon request:
Type Bits/KeyID Fingerprint (GnuPG (GPG) is preferred.)
GPG/ELG: 2048g/DE3E078A 0023 E86F A45A C46D 8243 1A7F 6FF2 84C1 3F5B F7CD
GPG/DSA: 1024D/3F5BF7CD (none for DSA keys)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Now ready for primetime! http://www.gnupg.org
-----END PGP SIGNATURE-----