https://bugzilla.novell.com/show_bug.cgi?id=383544
User rommel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383544#c5
Heiko Rommel changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rommel@novell.com
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #5 from Heiko Rommel 2008-05-14 03:32:20 MST ---
While testing the related maintenance update
YOU Patch No: 12156
ZYPP Patch No: 5231
MD5 sum: 72d3908e250b3900c4aaa08b17ca64b3
SUBSWAMPID: 17522
packages: suse-build-key
I came across three issues I would like to bring up:
1)
The keyring of user root traditionally held all the keys that are in
/usr/lib/rpm/gnupg/pubring.gpg (which is part of suse-build-key).
Starting with this update, the keyring of user root is not updated anymore.
I don't know if there are any issues with this on sle10 or code9, but this is
definitely an issue for sles8 (see point 3).
Maybe we should just add the keys to the keyring of user root to be save.
2)
The rpm keyring on sles8 has a PTF signing key
pub 1024D/B37B98A9 2005-05-11 SUSE PTF Signing Key
sub 1024g/6647760C 2005-05-11 [expires: 2008-06-30]
which was not updated by this maintenance update. Are we planning for a
separate update ? Do we need this key in the future at all ?
3)
The trustdb of the keyring was not updated during application of the patch.
As a consequence, the you client on sles8 fails to download the patch list on
the first start and throws an error as shown in the attached screen shot.
If start the you client a second time, gpg seems to have self-healed himself by
automatically updating the trustdb and then yast2 works as expected.
This look exactly like
https://bugzilla.novell.com/show_bug.cgi?id=103796#c35
from two years ago.
What is interesting in this context is that it was the trustdb of the keyring
of user root that has been updated self-healed.
/usr/lib/rpm/gnupg/trustdb.gpg just stayed the same (last mod time Aug 5 2004
on my ref host).
This is some evindence that we need to do 1)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.