On Sun, Feb 24, 2019 at 3:35 AM Michał Górny <mgo...@gentoo.org> wrote: > > Following the recent mailing list discussion indicating that developers > are taking GLEP 63 as only source of truth about OpenPGP keys, and can > make assumption that if encryption key is not listed there they should > not have one. Amend the specification to extend it beyond the previous > limited scope of commit signing, and require an encryption key > appropriately. This matches the GnuPG defaults.
Does GLEP 63 actually match the gpg defaults? That is, if you generate a gpg key and accept every default value will the key be acceptable? If not, could we get some updated documentation as to how to generate a minimally compliant key, similar to: https://www.gentoo.org/glep/glep-0063.html#bare-minimum-requirements -- Rich
