Bug#923668: apt update says "Signed file isn't valid", but apt-key verify passes

On Sun, Mar 03, 2019 at 10:42:42AM -0400, David Bremner wrote: > Julian Andres Klode writes: > > The Release.gpg must be ASCII armored, as documented in: […] > apt-key ("SUPPORTED KEYRING FILES") be updated? I'm not very happy with > the wiki as the primary/only documentation. The apt-secure

Bug#923668: apt update says "Signed file isn't valid", but apt-key verify passes

David Bremner writes: > Julian Andres Klode writes: >> >> The Release.gpg must be ASCII armored, as documented in: >> >> https://wiki.debian.org/DebianRepository/Format#A.22Release.22_files >> >> Following the recent CVE, checks where added that the Release.gpg >> contains only such

Bug#923668: apt update says "Signed file isn't valid", but apt-key verify passes

Julian Andres Klode writes: > > The Release.gpg must be ASCII armored, as documented in: > > https://wiki.debian.org/DebianRepository/Format#A.22Release.22_files > > Following the recent CVE, checks where added that the Release.gpg > contains only such signatures, to prevent hiding packages (or

Bug#923668: apt update says "Signed file isn't valid", but apt-key verify passes

Package: apt Version: 1.8.0~rc4 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have an apt repo managed by mini-dinstall deb http://apt.tethera.net/debian unstable/ It's signed by my key in the debian keyring. This is working fine with stretch, and was working fine