{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifm7ceouxdceqqh2dvuwvoj6fd2bke2jzgecmrb5kqsjiovxwbbhe",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mk5lo2tngga2"
  },
  "path": "/t/multiple-vulnerabilities-found-in-gnupg/34457#post_5",
  "publishedAt": "2026-04-23T06:29:44.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "beantaco:\n\n> GnuPG is no longer (aims to be) compliant to OpenPGP\n\nThis is not actually true as Gnupg is still compliant with openpgp spec rfc 4880 which is still the most widely supported version by most applications. So they are making it backward compatible. Its the newest openpgp spec rfc 9580 on which the gnupg diverges on , but this spec is very much new (released in 2024) and is yet to have any adoption in any major applications , apart from maybe fedora which is bringing it but still cannot entirely replace gnupg because a lot of components still dependent on gnupg tools.\n\ni am no expert on encryption and specs so , i wouldn’t comment on which protocol is better , but certainly feels that gnupg would still be continued to use for most applications for foreseeable future.\n\nThere is a concern about interoperability between the 2 if they continue to move forward with their own specs , but we have to see how things play out going ahead.",
  "title": "Multiple Vulnerabilities Found in GnuPG"
}