-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Tuesday 2006-05-02 at 10:45 +0200, Marcus Meissner wrote:
> You must recreate the SHA1sums in the /content file to match the
> changed files (MD5SUMS and packages for instance) and sign it afterwards.
>
> Also all meta file needs to be listed there, see CD1/content
Er... what would be the solution for people that, like me, already updated
from RC2 to RC3 using the dvd?
I get this error:
File content
is signed with the following GnuPG key, but the integrity check failed:
ID: A84EDAE89C800ACA
Fingerprint: 79C1 79B2 E1C8 20C1 890F 9994 A84E DAE8 9C80 0ACA
Name: SuSE package Signing Key <[EMAIL PROTECTED]>
This means that the file has been changed by accident or by an attacker
since the repository creator signed it. Using it is a big risk
for the integrity ans security of your system.
Use it anyway?
which I have got to tell it to ignore several times.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFEVyvstTMYHG2NR9URAiPuAJ9mjaJcIGd52yr2ic6k4IZv/Q5h2wCfeA89
UwGwowiUlmGVG2anfS1Y4cM=
=cRKV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
