Op 16-05-17 om 11:53 schreef Peter Miller:
Frank,
Yes, they do, but associated with Wheezy and Jessie, by the looks?
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg
----------------------------------------------------------
pub rsa4096 2012-04-27 [SC] [expires: 2020-04-25]
A1BD 8E9D 78F7 FE5C 3E65 D8AF 8B48 AD62 4692 5553
uid [ unknown] Debian Archive Automatic Signing Key
(7.0/wheezy) <ftpmas...@debian.org>
/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
----------------------------------------------------------
pub rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
126C 0D24 BD8A 2942 CC7D F8AC 7638 D044 2B90 D010
uid [ unknown] Debian Archive Automatic Signing Key
(8/jessie) <ftpmas...@debian.org>
Are these in the right places? What is the first half of the full key?
Those are the correct keys. My system has the same ones. Don't be misled
by the names. They were created in a time when Wheezy and Jessie were
current, but they're still valid. As far as I'm aware, no Stretch
specific keys have been created yet.
I'm afraid I don't understand why synaptic complains about the
signatures of the InRelease files. They're signed with the right keys,
which are avaiable on your system.
Does the same thing happen if you run apt-get update in a terminal?
Maybe clearing out the list cache by deleting the contents of
/var/lib/apt/lists will help (bit of a long shot, but who knows...?).
Are the apt and gnupg packages up to date? I have apt 1.4.1 and gnupg
2.1.18-6 here.
Regards,
Frank
