I'm unaware of this consensus, and I'm also unaware of the implications the decisions made by the OpenPGP WG may have in the future. Could you tell me the specifics of these protocol changes, and why LibrePGP is the responsible party? I'd rather have the criticisms being made by the LibrePGP team *be addressed,* rather than have them be ignored, and swept under the rug.
https://gnupg.org/blog/20260320-some-criticism-matter.html I'd also like to see what the OpenPGP WG has to say about LibrePGP, and again, *address* the concerns of the LibrePGP maintainers. In particular, since you are on the RHEL crypto team, why don't you lead this discussion? Sent with Proton Mail secure email. On Monday, July 20th, 2026 at 14:54, Simo Sorce <[email protected]> wrote: > On Mon, 2026-07-20 at 17:44 +0000, CS Sushi Man via devel wrote: > > In regards to the statement I've made about contacting the > > *former* GnuPG team, I found a list of reasons for this fork here: > > > > https://librepgp.org/#about > > > > The reason is that the GnuPG maintainer did not want to accept the > consensus reached within the openpgp WG, which all other > implementations had no problems with. > > In fact their statement is really ironic given LibrePGP actually is the > cause of new ecosystem fragmentation at the protocol level which did > not exist before. > > In any case the evaluations has already been made and the decision is > to stick with the IETF standard instead of following a single > implementer down a wrong road. > > Simo. > > -- > Simo Sorce > Distinguished Engineer > RHEL Crypto Team > Red Hat, Inc > > -- -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
