Skip to content

Commit 1d27425

Browse files
committedJul 21, 2016
Add a README.md
1 parent 8f83c1c commit 1d27425

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed
 

‎README.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
This repository contains the keys of the hackage root key holders.
2+
3+
This is primarily to help us keep track, but it also serves the purpose of
4+
letting 3rd parties verify that the root keys are indeed held by the people
5+
who ought to hold them.
6+
7+
8+
Verifying root keys
9+
=====================
10+
11+
Several of the root key holders have sent a gpg-signed email that confirms
12+
the public part of the hackage root key that they hold, and that they
13+
understand their responsibilities as a hackage root key holder.
14+
15+
So anyone can verify the root key set by:
16+
17+
1. Reading each of these emails, checking that the public key mentioned in
18+
the email corresponds to the one in the hackage root metadata file
19+
(`root.json`).
20+
2. Using gpg to verify that the emails were sent by the correct people.
21+
This requires that you have previously joined the gpg web of trust
22+
involving the hackage root key holders.
23+
24+
25+
Note that some of the emails use detached signatures and some use inline
26+
signatures. Where there is just a `.email` file and no `.sig` use
27+
`gpg --verify $name.email`, where there is a separate `.sig` then use
28+
`gpg --verify $name.sig $name.email`
29+
30+
So you can check the current signatures like so:
31+
32+
$ gpg --verify adam-gundry.email.sig adam-gundry.email
33+
$ gpg --verify gershom-bazerman.email.sig gershom-bazerman.email
34+
$ gpg --verify johan-tibell.email
35+
$ gpg --verify john-wiegley.email.sig john-wiegley.email
36+
$ gpg --verify norman-ramsey.email
37+

0 commit comments

Comments
 (0)
Please sign in to comment.