Re: [gentoo-dev] Git, GPG Signing, and Manifests

[Rich Freeman]

On Fri, Jul 17, 2015 at 8:36 AM, Rich Freeman <rich0@g.o> wrote:
> On Fri, Jul 17, 2015 at 12:42 AM, Brian Dolbec <dolsen@g.o> wrote:
>>
>> I don't know tbh, most are already signed, with the git migration, the
>> strongly recommended commit signing will become MANDATORY.
>>
>> So, we are at 50 devs with valid gpg keys now, with 200 more gpg keys
>> listed in LDAP that fail to meet the new spec.  PLEASE fix them or
>> create new keys...
>
> How does somebody know whether their key meets the spec or not?  I
> looked at the gentoo-keys website and didn't see any simple way to
> check.
>
> There was documentation on the gkeys utility for checking keys, but I
> ran into a few issues with this.
>

After waking up a bit more I configured a utf8 locale in my "clean
stage3" and the errors went away, and I was able to verify that my key
passed, with no encryption subkey (I don't intend to use this key for
anything but gentoo main repository signing).

Even so, it might not hurt to have a one-line way to check an
arbitrary gpg key for conformity by ID.  Otherwise we invite trial and
error with devs uploading what they hope are compliant keys, fixing
LDAP, waiting for seeds to be repopulated, then checking them.

-- 
Rich