[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

PGP -kc forgets a key, has corrupt output?



-----BEGIN PGP SIGNED MESSAGE-----

I am reposting this from comp.security.pgp.tech, where my plea was met only
with stony silence.

Can someone here help?  (Lars, do you know anything about this?)

I have read the pgp manpage and pgpdoc[12].txt files in their entirety, and
cannot figure out what the problem is.

Newsgroups: comp.security.pgp.tech
Subject: PGP -kc forgets a key, has corrupt output?
Date: 24 Jun 1997 13:05:01 GMT
Organization: Purdue University
Lines: 96
Sender: Branden Robinson <branden@cartoon.ecn.purdue.edu>
Message-ID: <5ooglt$r4o@mozo.cc.purdue.edu>
NNTP-Posting-Host: cartoon.ecn.purdue.edu
X-Newsreader: TIN [UNIX 1.3 unoff BETA 970622; sun4u SunOS 5.5]

Could someone enlighten me please?

I just recently signed the key of someone whose key is on my public
ring. pgp -kv on my public ring shows correct output, but pgp -kc makes
it appear that I have signed my own key twice, and leaves out the other
inidividual's information -- except for the fact that it recognizes his
signatures on my and other keys and expands it to his name.

I'm using pgp 2.6.3a from the pgp-us Debian package assembled by Lars
Wirzenius (moderator of comp.os.linux.announce, among other things).

Here is some sample output, edited for brevity.

[0] 205 apocalypse ~ > pgp -kvv | more
Pretty Good Privacy(tm) 2.6.3a - Public-key encryption for the masses.
(c) 1990-96 Philip Zimmermann, Phil's Pretty Good Software. 1996-03-04
Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc.
Distributed by the Massachusetts Institute of Technology.
Export of this software may be restricted by the U.S. government.
Current time: 1997/06/24 12:53 GMT

Key ring: '/home/branden/.pgp/pubring.pgp'
Type Bits/KeyID    Date       User ID
pub  1024/F6599E8D 1996/07/20 Bruce Perens <Bruce@Pixar.com>
[...]
pub  1024/D23450F9 1997/06/21 Branden Robinson <branden@purdue.edu>
sig       D190E74D             Terran Lane <terran@ecn.purdue.edu>
sig       D23450F9             Branden Robinson <branden@purdue.edu>
pub  1024/D190E74D 1996/09/25 Terran Lane <terran@ecn.purdue.edu>
sig       D23450F9             Branden Robinson <branden@purdue.edu>
sig       C38884A5             (Unknown signator, can't be checked)
sig       20D3D431             (Unknown signator, can't be checked)
sig       914C58A9             (Unknown signator, can't be checked)
sig       47D738C1             (Unknown signator, can't be checked)
sig       B29DE5FD             (Unknown signator, can't be checked)
sig       D7BD2F75             Timothy M. Stough <stough@ecn.purdue.edu>
sig       9C2A5CDD             (Unknown signator, can't be checked)
sig       FC0C02D5             Eugene H. Spafford <spaf@cs.purdue.edu>
sig       D190E74D             Terran Lane <terran@ecn.purdue.edu>
6 matching keys found.

As you see, my own key is next to last in this output, followed by Terran
Lane's, which I signed.

Now for the strange part.

[0] 206 apocalypse ~ > pgp -kc | more
Pretty Good Privacy(tm) 2.6.3a - Public-key encryption for the masses.
(c) 1990-96 Philip Zimmermann, Phil's Pretty Good Software. 1996-03-04
Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc.
Distributed by the Massachusetts Institute of Technology.
Export of this software may be restricted by the U.S. government.
Current time: 1997/06/24 12:56 GMT

Key ring: '/home/branden/.pgp/pubring.pgp'
Type Bits/KeyID    Date       User ID
pub  1024/F6599E8D 1996/07/20 Bruce Perens <Bruce@Pixar.com>
[...]
pub  1024/D23450F9 1997/06/21 Branden Robinson <branden@purdue.edu>
sig!      D190E74D 1997/06/24  Terran Lane <terran@ecn.purdue.edu>
sig!      D23450F9 1997/06/21  Branden Robinson <branden@purdue.edu>
sig!      D23450F9 1997/06/24  Branden Robinson <branden@purdue.edu>

And Terran Lane's key, which I signed, is completely absent from this
output.

Is this a bug in 2.6.3a, am I misinterpreting this output, or has my public
ring become corrupted?

Please help.  Apologies for not signing this message "correctly",
my newsreader does not integrate well with pgp.

Of course, pgp-signed or -encrypted mail is welcome.

- -- 
G. Branden Robinson
Purdue University
branden@purdue.edu
http://www.ecn.purdue.edu/~branden/

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv

iQCVAwUBM7H7qKiRn0nSNFD5AQEtggP/ZkjHBv9Ko4dANFr/orXmtXYHtwlGbHFY
YNDx8kH6zUUpfvMPyhFIuTjUX/s4roAm7lCOaX6G8BzC1DonYmK7pVIdgslev0DC
lfDkOrXPUNtSOmdVOnttIwv+wdtiS3zI6YICIg4GmOx3KyejwigDcTjvw3cxpZ4X
8XOETWqtBsM=
=vvnE
-----END PGP SIGNATURE-----


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: