On Thu, Nov 21, 2024 at 09:16:20PM +0100, Julian Andres Klode wrote: > I've just finished more or less, adjusting the APT test suite > to test gpgv-sq. I plan to upload APT that tests gpgv-sq > tomorrow. This ensures full compatibility between apt and > gpgv-sq going forward. > > After that migrates to testing next week, I want to make > the switch: APT by default should use gpgv-sq. Previous > discussions with the security team did not reveal any > blockers for that, despite the strenuous nature of > security updates for Rust packages.
I have been informed I did not include the reasons and it's become
clear not everyone already knows the background here:
1. The GnuPG upstream forked the OpenPGP standard into his own
thing called LibrePGP, and GnuPG 2.4 implements that new thing
and is by default incompatible with other OpenPGP implementations.
2. GnuPG 2.4 is in experimental and patching out the LibrePGP
stuff is kind of necessary for it to be acceptable for release.
3. GnuPG 2.2 which is in unstable reaches its end of life in a couple
of weeks.
4. The GnuPG implementation quality has issues, such as silently
ignoring options not relevant to the current operation/mode,
producing no clear errors on expired signatures (they show
up as valid, just not as "good", but not as "bad" either),
and some features are very much unsafe, for example, the
new --assert-pubkey-algo feature accepts
<operator><name><size>
as the syntax, so it looks at >=ed448 and accepts ed25519
as being stronger because 25519 >= 448, whereas it is
the weaker curve.
Switching to gpgv-sq gets us out of this hole now while
we are waiting for the Stateless OpenPGP standard and
implementations of it to mature such that we can switch
to sqopv (| rsopv | sopv-gpgv | gosop).
Also it's written in a memory safe language which might make
the OpenPGP packet parsing safer :D
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
signature.asc
Description: PGP signature
