Re: Problem with /var/lib/YaST2/you/syncfile (SLES 9 SP 4)

J.H.M. Dassen (Ray)   [26.05.2008 15:33]:
> On Wed, May 21, 2008 at 16:28:20 +0200, Werner Flamme wrote:
>> 2008-05-20 20:23:53 (15424): Retrieving patch-10611: "Recommended update
>> for man-pages"
>> 2008-05-20 20:23:53 (15424): Error: Signature check failed.
> 
>> So, what can I do to get rid of this signature check error in patch-10611?
> 
> Did you have a look at
> 	http://en.opensuse.org/SDB%3AYOU_Reports_Problems_Verifying_Patch_Signatures
> ?
> 
> HTH,

Hi Ray,

yes, I had, months ago... :-( However, I found my problem on
http://en.opensuse.org/SDB:YOU_or_RPM_Report_Problems_Verifying_Package_Signatures,
but the solution did not work...


First page, first reason: GPG keys corrupted:

#  gpg --no-default-keyring --keyring /usr/lib/rpm/gnupg/pubring.gpg
--verbose --list-keys
/usr/lib/rpm/gnupg/pubring.gpg
------------------------------
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <[email protected]>
sig 3       9C800ACA 2004-06-22   SuSE Package Signing Key <[email protected]>
sig         000AABA4 2001-01-25   [User id not found]
sig         3D25D3D9 2001-01-25   SuSE Security Team <[email protected]>
sub  2048g/8495160C 2000-10-19 [expires: 2008-06-21]
sig         9C800ACA 2004-06-22   SuSE Package Signing Key <[email protected]>

pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <[email protected]>
sig         B1CA3C45 1999-03-06   [User id not found]
sig         3D25D3D9 1999-03-06   SuSE Security Team <[email protected]>
sig         000AABA4 2001-06-06   [User id not found]
sig         CEFC9215 1999-08-15   [User id not found]
sig         B0DFF780 2000-11-21   [User id not found]

pub  1024D/0DFB3188 2005-01-18 Open Enterprise Server <[email protected]>
sig 3       0DFB3188 2005-01-18   Open Enterprise Server
<[email protected]>

pub  1024D/15C17DEB 2003-10-28 Java Desktop Package Signing Key
<[email protected]>
sig 3       15C17DEB 2003-10-28   Java Desktop Package Signing Key
<[email protected]>

pub  4096R/A1912208 2006-05-16 Novell Provo Build (Contact
[email protected]) <[email protected]>
sig 3       A1912208 2006-05-16   Novell Provo Build (Contact
[email protected]) <[email protected]>
sig 3       9C800ACA 2006-05-17   SuSE Package Signing Key <[email protected]>

pub  1024D/7E2E3B05 2006-05-24 Novell Provo Build (Contact
[email protected]) <[email protected]>
sig 3       7E2E3B05 2006-05-24   Novell Provo Build (Contact
[email protected]) <[email protected]>
sig 3       9C800ACA 2006-05-29   SuSE Package Signing Key <[email protected]>

Does this show "corrupted GPG files"? I dunno...

First page, second cause: time in far future
# ntpq -p
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
 LOCAL(0)        LOCAL(0)        10 l   70 1024  377    0.000    0.000
 0.001
*ntp.leipzig.ufz .PPS.            1 u   69 1024  377    0.242   -0.327
 0.865
+141.65.171.172  192.53.103.108   2 u   67 1024  377    3.456    1.512
 2.908

The machine is synced well with our company's time server (BTW,
141.65.171.172 is a SLES10 inside an ESX :-))

Second page, cause "missing RPM keys":
# rpm -qa 'gpg-pubkey*' | sort | uniq
gpg-pubkey-0dfb3188-41ed929b
gpg-pubkey-11f63c51-3c7dc11d
gpg-pubkey-15c17deb-3f9e80c9
gpg-pubkey-3d25d3d9-36e12d04
gpg-pubkey-9c800aca-40d8063e
gpg-pubkey-b37b98a9-443d101a

Ah, yes, last time I looked, there was no key list at the bottom of the
page. I see that #  gpg-pubkey-b37b98a9-6647760c and
gpg-pubkey-b37b98a9-42820f17 are missing.

I imported the keys into the gpg keyring, now the output is a bit
longer, a new key is there:

pub  1024D/B37B98A9 2005-05-11 SUSE PTF Signing Key <[email protected]>
sig 3     X 9C800ACA 2006-02-01   SuSE Package Signing Key <[email protected]>
sig 3       B37B98A9 2005-05-11   SUSE PTF Signing Key <[email protected]>
sig 3       B37B98A9 2006-04-12   SUSE PTF Signing Key <[email protected]>
sub  1024g/6647760C 2005-05-11 [expires: 2008-06-30]
sig         B37B98A9 2006-04-12   SUSE PTF Signing Key <[email protected]>

I'm led then to download PTFkey-install.sh. That was done by YOU some
weeks ago. However, I put the script on the machine - but why is there

# cat PTFkey-install.sh
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

#!/bin/bash

rootKeyring="/root/.gnupg/pubring.gpg"
...

at the beginning of the file? This does not run... After cleaning the
mess up, it ran, but no new key in RPM.

Anyway:
# /var/lib/YaST2/you/syncfile
Types of patches to be installed: security recommended patchlevel
Server URL: https://you.novell.com/update/
Server Name:
Directory File:
Path 0: ./x86_64/update/SUSE-SLES/9/patches
No patches have been installed.
Got patches.
Types of patches to be installed: security recommended patchlevel
Server URL: https://you.novell.com/update/
Server Name:
Directory File:
Path 0: ./x86_64/update/SUSE-CORE/9/patches
No patches have been installed.
Error processing patches: ERROR(You:RPM has invalid signature.)
Types of patches to be installed: security recommended patchlevel
Server URL: https://you.novell.com/update/
Server Name:
Directory File:
Path 0: ./i386/update/SUSE-SLES/9/patches
No patches have been installed.
Got patches.
Types of patches to be installed: security recommended patchlevel
Server URL: https://you.novell.com/update/
Server Name:
Directory File:
Path 0: ./i386/update/SUSE-CORE/9/patches
No patches have been installed.
Got patches.


Thanks for the help, but it wasn't the solution :-(

Regards,
Werner

-- 
Werner Flamme, Abt. WKDV
Helmholtz-Zentrum für Umweltforschung GmbH - UFZ
Permoserstr. 15 - 04318 Leipzig
Tel.: (0341) 235-1921 - Fax (0341) 235-451921
http://www.ufz.de - eMail: [email protected]
_______________________________________________
suse-sles-e mailing list
[email protected]
http://listx.novell.com/mailman/listinfo/suse-sles-e