On 2025-01-13, Daniel Kahn Gillmor <d...@debian.org> wrote: > The idea that the other members of the working group were "forcing the > schism" doesn't line up with my experience. Werner decided to step away > from the process of standardizing something in an open and interoperable > way.
At some point, one might need to step away if others insist on sillyness (my wording) One of the 'big points' as I understood it was doing aead in 3 different ways, two optional. To quote the upstream documentation of another Openpgp project: | openpgp.enums.aead.gcm; // Default, native in WebCrypto and Node.js | openpgp.enums.aead.ocb; // Non-native, but supported across RFC 9580 implementations | openpgp.enums.aead.eax; // Native in Node.js Defaulting to a mode that is optional in the spec and thus not all implementations support it. Having 3 ways of doing things the same thing is to me just silly from an engineering perspective. And having some of it optional when it really isn't (and defaulting to one of the optionals) in the spec is just weird. /Sune
