Re: etch pam update not signed
Hi Tom,
On Wed, May 27, 2009 at 10:04:23AM -0400, Tom Vier wrote:
> Anyone know why these aren't signed (or signed by an unknown key)? I
> installed the latest keyring.
>
> WARNING: The following packages cannot be authenticated!
> libpam-runtime libpam0g libpam-modules libpq4
> Install these packages without verification [y/N]?
Verifying manually for
http://security.debian.org/dists/etch/updates/Release{,.gpg}:
] hesso@caro:/tmp>gpg --verify Release.gpg Release
] gpg: Signature made 24 May 2009 14:12:02 MEST using RSA key ID 55BE302B
] gpg: Good signature from "Debian Archive Automatic Signing Key (5.0/lenny) <ftpmaster@debian.org>"
] gpg: WARNING: This key is not certified with a trusted signature!
] gpg: There is no indication that the signature belongs to the owner.
] Primary key fingerprint: 150C 8614 919D 8446 E01E 83AF 9AA3 8DCD 55BE 302B
] gpg: Signature made 24 May 2009 14:12:02 MEST using DSA key ID 6070D3A1
] gpg: Good signature from "Debian Archive Automatic Signing Key (4.0/etch) <ftpmaster@debian.org>"
] gpg: WARNING: This key is not certified with a trusted signature!
] gpg: There is no indication that the signature belongs to the owner.
] Primary key fingerprint: A999 51DA F9BB 569B DB50 AD90 A70D AF53 6070 D3A1
Looks good to me. You might want to check /etc/apt/trusted.gpg and
the state of your debian-archive-keyring package.
Regards,
Jan
Reply to: