Post #2814557
2026-04-25 08:28 UTC
@aspensmonster@tenforward.social @petelawler@mastodon.social @hko@floss.social many of us suspect that the root of the problem is the age of gnupg’s codebase, which bakes in a lot of assumptions and premature optimisations, and which doesn’t have any unit tests or continuous integration. It’s a codebase that few outsiders understand and which few insiders are confident about making major changes to.
Replies (2)
-
@andrewg@mastodon.ie 2026-04-25 08:31
@aspensmonster@tenforward.social @petelawler@mastodon.social @hko@floss.social the differences between rfc9580 and “librepgp” can then be interpreted by asking “how easy would it be to implement this in the gnupg codebase without breaking it?”.
-
@hko@floss.social 2026-04-25 08:31
@andrewg@mastodon.ie @aspensmonster@tenforward.social @petelawler@mastodon.social I very much agree with Andrew's analysis. (Fwiw, I think there is no conceivable monetary incentive for GnuPG to fork away from the OpenPGP standard.)