4 ms·
GnuPG has by default started emitting keypairs with a preference for the LibrePGP version of the OCB block cipher mode. That mode is not compatible with what th
by upofadown 3y ago
GnuPG has by default started emitting keypairs with a preference for the LibrePGP version of the OCB block cipher mode. That mode is not compatible with what the other faction is doing and is not generally supported in any case. Arch[1] and other distributions have apparently patched this default out.
Is Rpgp emitting any new block cipher modes or generating keys that might cause such emission in the future? The risk here is a sort of incompatibility nightmare where decryption becomes a crap shoot.
My article on this mess:
https://articles.59.ca/doku.php?id=pgpfan:schism https://articles.59.ca/doku.php?id=pgpfan:schism
[1] https://wiki.archlinux.org/title/GnuPG#Disable_unsupported_AEAD_mechanism https://wiki.archlinux.org/title/GnuPG#Disable_unsupported_A...
- deleted 3y ago[deleted]
- wiktor-k 3y agoYep, the schism is really bad for the end users and based on my "insider" knowledge it doesn't seem like the resolution is near. The tl;dr is that GnuPG basically forked OpenPGP into https://librepgp.org/ https://librepgp.org/
- dignifiedquire 3y agoWhile rpgp is slowly gaining support for this format (the aid users to be able to talk to anyone they want) it will keep emitting the broadest compatible format for a while by default, until the whole ecosystem has upgraded. The aggressive stance from gnupg is really hurting people and removes one of the biggest benefits of pgp, broad interop with compliant implementations.
- upofadown 3y agoEach faction has a seemingly legitimate position. My understanding is that there are no cryptographic weaknesses in the existing block cipher mode (SEIP) so there are no downsides to just doing that indefinitely.