[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-devel
Subject:    OpenPGP compatibility in GnuPG 2.3
From:       Vincent Breitmoser via Gnupg-devel <gnupg-devel () gnupg ! org>
Date:       2022-12-12 18:56:17
Message-ID: 19bd309c-f657-fbc7-162d-140bb8d98db0 () my ! amazin ! horse
[Download RAW message or body]

Hey Werner and list,

I had (semi-)recently asked a question on this commit at dev.gnupg.org, 
and was redirected by Werner to this list.

https://dev.gnupg.org/rG4583f4fe2e11b3dd070066628c3f16776cc74f72

If I understood this commit correctly, it turns the behavior that was 
formerly part of the `--rfc4880bis` flag into the default.
Specifically, that means that the packets from 
[draft-koch-openpgp-2015-rfc4880bis] are now used by default.
This commit was merged into master, so my understanding is that it is 
now in the GnuPG 2.3 release line.

The OpenPGP working group has decided on 2022-10-10 to base their 
revision of the OpenPGP standard
on the packet format from crypto-refresh, rather than 
draft-koch-openpgp-2015-rfc4880bis.
As such, the behavior that is made the default by this commit will 
produce certificates that will be
incompatible with the upcoming OpenPGP standard.

Given that this commit was merged roughly two weeks after the 
aforementioned decision, should this be
understood that GnuPG intends to focus on its own packet format instead 
of standardized OpenPGP?

It would be interesting to hear what the intent and roadmap of GnuPG are 
in this regard.

Thanks in advance

   - V

[draft-koch-openpgp-2015-rfc4880bis]: 
https://datatracker.ietf.org/doc/draft-koch-openpgp-2015-rfc4880bis/
[decided]: 
https://mailarchive.ietf.org/arch/msg/openpgp/yayGaIen3DW6ixwrJkP-QcAcFSQ/


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

[prev in list] [next in list] [prev in thread] [next in thread]