| 1 |
On Sun, 13 Dec 2015 16:30:06 -0500 Mike Gilbert wrote: |
| 2 |
> On Sun, Dec 13, 2015 at 2:20 PM, Andrew Savchenko <bircoph@g.o> wrote: |
| 3 |
> >> Since signing is mandatory since the git migration, ahem, this means |
| 4 |
> >> that no one in the last 5 months(!) actually followed the documentation |
| 5 |
> >> (because that does NOT work!). I'm almost impressed, but, wow, this is |
| 6 |
> >> enterprisey. |
| 7 |
> > |
| 8 |
> > It is absolutely possible to create correct gpg key, put it into |
| 9 |
> > LDAP according to GLEP and to sign commits and pushes properly. |
| 10 |
> |
| 11 |
> If gkeys is as broken as Patrick describes, it might be helpful to |
| 12 |
> have step-by-step instructions for manually generating an appropriate |
| 13 |
> key. This would help new developers. |
| 14 |
|
| 15 |
GLEP 63 already contains detailed instructions of how to do this: |
| 16 |
https://wiki.gentoo.org/wiki/GLEP:63#Specifications_for_GnuPG_keys |
| 17 |
|
| 18 |
New devs only have to run |
| 19 |
$ gpg --gen-key |
| 20 |
follow instructions from GLEP 63, and upload key using |
| 21 |
$ gpgp --send-key $key_id |
| 22 |
|
| 23 |
|
| 24 |
Best regards, |
| 25 |
Andrew Savchenko |
Archives