| 1 |
On Fri, 17 Jul 2015 08:50:43 -0400 |
| 2 |
Rich Freeman <rich0@g.o> wrote: |
| 3 |
|
| 4 |
> On Fri, Jul 17, 2015 at 8:36 AM, Rich Freeman <rich0@g.o> |
| 5 |
> wrote: |
| 6 |
> > On Fri, Jul 17, 2015 at 12:42 AM, Brian Dolbec <dolsen@g.o> |
| 7 |
> > wrote: |
| 8 |
> >> |
| 9 |
> >> I don't know tbh, most are already signed, with the git migration, |
| 10 |
> >> the strongly recommended commit signing will become MANDATORY. |
| 11 |
> >> |
| 12 |
> >> So, we are at 50 devs with valid gpg keys now, with 200 more gpg |
| 13 |
> >> keys listed in LDAP that fail to meet the new spec. PLEASE fix |
| 14 |
> >> them or create new keys... |
| 15 |
> > |
| 16 |
> > How does somebody know whether their key meets the spec or not? I |
| 17 |
> > looked at the gentoo-keys website and didn't see any simple way to |
| 18 |
> > check. |
| 19 |
> > |
| 20 |
> > There was documentation on the gkeys utility for checking keys, but |
| 21 |
> > I ran into a few issues with this. |
| 22 |
> > |
| 23 |
> |
| 24 |
> After waking up a bit more I configured a utf8 locale in my "clean |
| 25 |
> stage3" and the errors went away, and I was able to verify that my key |
| 26 |
> passed, with no encryption subkey (I don't intend to use this key for |
| 27 |
> anything but gentoo main repository signing). |
| 28 |
> |
| 29 |
> Even so, it might not hurt to have a one-line way to check an |
| 30 |
> arbitrary gpg key for conformity by ID. Otherwise we invite trial and |
| 31 |
> error with devs uploading what they hope are compliant keys, fixing |
| 32 |
> LDAP, waiting for seeds to be repopulated, then checking them. |
| 33 |
> |
| 34 |
|
| 35 |
One of the things I really wanted to get into gkeys is a way to add a |
| 36 |
users ~/.gnupg dir imported into the gkeys system, that will help in |
| 37 |
that reagrds and make it more of a one stop shop for common gpg tasks. |
| 38 |
|
| 39 |
Also, I will try to get at least the gkeys-gen target keydir added to |
| 40 |
gkeys visibility in the next release. |
| 41 |
|
| 42 |
Oh, forgot to mention. I will send the gkeys spec-check report |
| 43 |
to the gentoo-core list for a start. Perhaps some of the devs can help |
| 44 |
us get the wiki help pages completed when they fix their keys and know |
| 45 |
the steps. I'm sure both Kristian and myself would appreciate a little |
| 46 |
help with that while we are explaining how to fix the failures. |
| 47 |
|
| 48 |
One of the slowdowns in completing those pages is creating anomymous |
| 49 |
gpg keys output for the wiki examples. I do not want to use devs real |
| 50 |
keys as examples (which of course would be easiest). |
| 51 |
|
| 52 |
-- |
| 53 |
Brian Dolbec <dolsen> |
Archives