Bug 74436 - Once touched by 1.0.7, keyring becomes unreadable elsewhere
Summary: Once touched by 1.0.7, keyring becomes unreadable elsewhere
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnupg
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-24 10:56 UTC by Kevin Sonney
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-01-23 18:25:24 UTC
Embargoed:


Attachments (Terms of Use)

Description Kevin Sonney 2002-09-24 10:56:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
Once a keyring is modified by gnupg 1.0.7, versions of gpg included with earlier
distros can no longer read it. When attempting a --list-keys on a 1.0.7
maintained pubring with an older version of gnupg, packet errors are generated.
See below for more. 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. modify an exisintg public keyring from psyche
2. attempt to list keys in that keyring on valhalla (7.3)
3. See the following error :
gpg: [don't know]: invalid packet (ctb=03)
gpg: read_keyblock: read error: invalid packet
gpg: enum_keyblocks(read) failed: invalid keyring


Actual Results:  This error happens on all available prior versions of GPG I
have to test - 1.0.6-0.6.x (from RHL 6.2) and 1.0.6-5 (from RHL 7.3). 

Expected Results:  I should see a list of keys, and I don't. 

Additional info:

Backporting 1.0.7 (from psyche) to 6.2 and 7.3 fixed the errors. in order to
compile on 6.x, LDAP had to be disabled in the .spec file.

Comment 1 Kevin Sonney 2002-09-24 14:12:44 UTC
addendum for completeness : also fails on AS 2.1 gnupg 1.0.6-3 (but that's not a
surprise)

Comment 2 Kevin Sonney 2003-01-23 18:25:24 UTC
Closing, since this is a GPG "feature" and not something Red Hat can fix.


Note You need to log in before you can comment on or make changes to this bug.