[PATCH 3/3] common: Add support for the new extended private key format.

Andre Heinecke aheinecke at intevation.de
Fri Apr 15 09:38:59 CEST 2016

Hi Justus,

On Thursday 14 April 2016 16:41:12 Justus Winter wrote:
> GnuPG 2.3+ will use a new format to store private keys that is both
> more flexible and easier to read and edit by human beings.  The new
> format stores name,value-pairs using the common mail and http header
> convention.
> This patch adds the parser and support code and prepares GnuPG 2.1 for
> the new format.

I feel a bit that this should have been discussed before implementing it. For 
any changes to key storage (public or private) I would have argued to switch 
to sqlite. The amount of Bugs and performance problems by using non-standard 
formats has been a problem in GnuPG in my (limited) experience.

Sqlite databases are also easily editable by power users with standard tools 
and you would not need yet another GnuPG specific file format with a parser etc.  
it would imo also solve your requirement to store meta data.


Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 648 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20160415/5322b58f/attachment.sig>

More information about the Gnupg-devel mailing list