1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
Greetings all, |
5 |
|
6 |
As of yesterday, GitHub now supports GPG signature verification [1]. |
7 |
As a result, when viewed through the GitHub mirror, all commits now |
8 |
have a widget that displays whether the GPG signature has been |
9 |
verified (via GitHub). To help facilitate this, it is highly |
10 |
recommend that all developers who use GitHub update their accounts to |
11 |
include their GPG public key [2] so that their commits can register as |
12 |
verified, where applicable. |
13 |
|
14 |
Just a disclaimer, I'm not endorsing the use of GitHub, nor advocating |
15 |
for it, simply indicating a new feature which it would be nice to see |
16 |
Gentoo developers on GitHub taking advantage of. |
17 |
|
18 |
- -- |
19 |
NP-Hardass |
20 |
|
21 |
[1] https://github.com/blog/2144-gpg-signature-verification |
22 |
[2] https://github.com/settings/keys |
23 |
-----BEGIN PGP SIGNATURE----- |
24 |
Version: GnuPG v2 |
25 |
|
26 |
iQIcBAEBCAAGBQJXBUzdAAoJEBzZQR2yrxj7IWsQALU1drSsPdV02PJVExz3xuVL |
27 |
gVB+8D6srxF9A2tlE6hBSPQCYkX9H0lHvt81WLOhKrIGxaNJJuwXlMKlQascpIer |
28 |
+OeLwA/5Nhn3MukOQrQGEUEP9EKaj8DqpoeqEzoshQHrdoj3thrxPoYjntRl+Ceq |
29 |
GH9gctvPyHAVXbZlKQ+T6yKOVlwLWeDNUkQAjW9hUbu+t33lO51PjqTto7tdj1yh |
30 |
lo12J4xu0lShBduJPomjrv9DH+rZm5dh4fC68d0wSVX+fdScLcVvgDJoxB3jsAHU |
31 |
IQs7iL0DToLQ2lkBMz0aZdwj8LRL0vGjipSGikvS+R9zxS/5elu2WvbGjrAOv51u |
32 |
nXpA3iQmo90k1VIm9VpU+2DxfPxqB0jIpc+91umKvGOlb4ySECc4C9OGn+jQXKwY |
33 |
fW/T/3zCik2dLmS02hUaZd5IbbnZhaRy7Y2VF17IdddP6V5SLvVahv431ezkmFR/ |
34 |
91PzD6ji5+Xti+dagVEWqoW6r7xUM9MBX113gicrT/3A/gSBW3DFtc/iDjjp+ABd |
35 |
HwI4mfCxEIl2p8y1YYfI3jgddMxcZpkaiQ/Av26PvUfNCN/lK3gbxiCMfuEcJZ5z |
36 |
gzFULA3r2Qf3Vz/8diQjf8lRLt2vjz7NDDcT0s7PE+xXJ/I2DmjAP9f8NJZ4sZ/X |
37 |
4uOd3r3sHkh9BcCKGCv1 |
38 |
=TanJ |
39 |
-----END PGP SIGNATURE----- |