Re: update Kimsufi, problème signature
Bonjour Raphaël,
j'ai trouvé une indication qui est sur une liste
Debian et voici le rtfm :
http://forums.debian.net/viewtopic.php?t=141778
serait il possible de vérifier les version
des paquets "keyring" ?
dpkg -l |awk ' /keyring/ {print $2,$3}'
deb-multimedia-keyring 2016.8.1
debian-archive-keyring 2021.1.1
debian-ports-archive-keyring 2020.02.02
emdebian-archive-keyring 2.2
gnome-keyring 3.36.0-1
gnome-keyring-pkcs11:amd64 3.36.0-1
libpam-gnome-keyring:amd64 3.36.0-1
pkg-mozilla-archive-keyring 1.2+nmu1
Merci
@+
Bernard
----- Mail original -----
> De: "Raphaël POITEVIN" <raphael.poitevin@gmail.com>
> À: debian-user-french@lists.debian.org
> Envoyé: Mardi 20 Avril 2021 15:52:04
> Objet: update Kimsufi, problème signature
>
> Bonjour,
>
> Pour aider une petite asso, je fais quelques maintenances sur leur
> Kimsufi. L’année dernière, j’ai fait une migration de Debian 8 vers
> 9,
> puis 9 vers 10.
>
> Je n’ai pas fait attention si ce problème faisait suite à la mise à
> jour, mais aujourd’hui que je remets la main dessus :
>
> # apt-get update
> Get:1 http://debian.mirrors.ovh.net/debian buster-updates InRelease
> [51.9 kB]
> Get:2 http://debian.mirrors.ovh.net/debian buster-backports InRelease
> [46.7 kB]
> Err:1 http://debian.mirrors.ovh.net/debian buster-updates InRelease
> The following signatures couldn't be verified because the public
> key
> is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY
> 648ACFD622F3D138
> Err:2 http://debian.mirrors.ovh.net/debian buster-backports
> InRelease
> The following signatures couldn't be verified because the public
> key
> is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY
> 648ACFD622F3D138
> Get:3 http://security.debian.org buster/updates InRelease [65.4
> kB]
> Err:3 http://security.debian.org buster/updates InRelease
> The following signatures couldn't be verified because the
> public
> key is not available: NO_PUBKEY AA8E81B4331F7F50 NO_PUBKEY
> 112695A0E562B32A
> Get:4 http://ftp-stud.hs-esslingen.de/debian buster InRelease
> [121
> kB]
> Err:4 http://ftp-stud.hs-esslingen.de/debian buster InRelease
> The following signatures couldn't be verified because the
> public
> key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY
> 648ACFD622F3D138 NO_PUBKEY DCC9EFBF77E11517
> Reading package lists... Done
> W: GPG error: http://debian.mirrors.ovh.net/debian
> buster-updates InRelease: The following signatures couldn't
> be
> verified because the public key is not available: NO_PUBKEY
> 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138
> E: The repository 'http://debian.mirrors.ovh.net/debian
> buster-updates InRelease' is not signed.
> N: Updating from such a repository can't be done securely,
> and
> is therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> W: GPG error: http://debian.mirrors.ovh.net/debian
> buster-backports InRelease: The following signatures couldn't
> be
> verified because the public key is not available: NO_PUBKEY
> 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138
> E: The repository 'http://debian.mirrors.ovh.net/debian
> buster-backports InRelease' is not signed.
> N: Updating from such a repository can't be done securely,
> and
> is therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> W: GPG error: http://security.debian.org buster/updates
> InRelease: The following signatures couldn't be verified
> because
> the public key is not available.
>
> Essayé avec d’autres dépôts, même chose.
>
> J’ai vérifié les empreintes des clés de /etc/apt/trusted.gpg.d, ça
> semble conforme avec :
> https://ftp-master.debian.org/keys.html
>
> Merci,
Reply to: