Mailing List Archive: [jgg@ualberta.ca: Creating things PGP 2 will read]

[jgg@ualberta.ca: Creating things PGP 2 will read]

May 11, 1999, 11:57 PM

Post #1 of 3 (1537 views)

See GnuPG's README file: It is signed by GnuPG and PGP can handle it.

The trick is, that you can't pipe the input to gpg becuase gpg is then
forced to used partial length headers - something pgp 2 doesn't know
about.

pgp --clearsign jnk

is allo need.

----- Forwarded message from Jason Gunthorpe <jgg@ualberta.ca> -----

Date: Wed, 12 May 1999 04:57:41 +0200
From: Jason Gunthorpe <jgg@ualberta.ca>
To: gnupg-users@lists.gnupg.org
Subject: Creating things PGP 2 will read
X-Diagnostic: Not on the accept list

Hi all,

I have had excellent luck in making GPG (with the RSA and IDEA modules)
able to read PGP 2.6 signatures and encrypted messages. However, I have
never been able to get GPG to generate anything that PGP 2.6 will
understand :< The output from GPG works entirely fine with GPG itself.

Is there some manner of options that can make this work? I am using the
command:

#cat jnk | gpg --rfc1991 --no-comment --clearsign > enc

And PGP gets as far as:

#cat enc | pgp

WARNING: Bad signature, doesn't match file contents!

Bad signature from user "Jason Gunthorpe <jgg@gpu.srv.ualberta.ca>".
Signature made 1999/05/12 02:57 GMT using 1024-bit key, key ID 35261E21

So it understand the packet but I presume it must be hashing differently?

Thanks,
Jason

----- End forwarded message -----

--
Werner Koch at guug.de www.gnupg.org keyid 621CC013

Re: [jgg@ualberta.ca: Creating things PGP 2 will read] [ In reply to ]

wk at isil

May 17, 1999, 1:44 AM

Post #2 of 3 (1470 views)

Permalink

Jason Gunthorpe <jgg@ualberta.ca> writes:

> I'm confused, why would you need any sort of variable/partial length
> mechansim when generating an ascii armoured signature? Don't you suck the
> whole text in and then compute the digest on the fly?

My box has ony 64 megs and I think there are messages which are much
larger :-) Being compatible to PGP2 is not a goal for GnuPG. I do as
much as I can but only up to a level where it does not break the
design of a good Unix program.

--
Werner Koch at guug.de www.gnupg.org keyid 621CC013

Re: [jgg@ualberta.ca: Creating things PGP 2 will read] [ In reply to ]

wk at isil

May 20, 1999, 3:04 AM

Post #3 of 3 (1489 views)

Permalink

Jason Gunthorpe <jgg@ualberta.ca> writes:

> I think I found the problem here :> I was originally talking about clear
> signed text messages which gpg seems to handle just fine through a pipe. I
> can understand why an ascii armored one would not work now (can you
> confirm that clear signing works in a PGP2 compatible manner with a pipe?)

Yes it should work; i sign the README file this way.

> My problem was that the message I was trying to sign causes gpg to
> consistently produce a signature that pgp 2 will not read (see the last

I'm currently working on that.

--
Werner Koch at guug.de www.gnupg.org keyid 621CC013