blob: 1d2c3668efaebe69ba2c90a0c19d540ede0ef95d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
After making sure a gpg2 with mailing list support is in your patch,
run test.sh as follows (when you run it, it will ask for two
passwords, use the password 'a'):
# ./test.sh
***************
Generating a user key (use a password of 'a').
***************
'Some User <[email protected]>'
***************
Importing some public keys.
Running: gpg2 --batch --import keys.gpg
***************
***************
Set the password to 'a'
***************
***************
Creating mailing list.
Running: gpg2 --batch --quick-gen-mailing-list-key gnupg-devel <[email protected]>
***************
'gnupg-devel <[email protected]>'
...
To get more verbose output, run test.sh with the -v flag. To get even
more output, change the gpg2 invocations to include --debug=packet.
A summary of the commands:
--mailing-list-key-gen
--quick-gen-mailing-list-key 'Name <[email protected]>'
Create a new mailing list key.
--mailing-list-add-sub ML-KEYID SUB-KEYID...
--mailing-list-add-rm ML-KEYID SUB-KEYID...
Add or remove one or more subscribers from the mailing list.
--mailing-list-subs ML-KEYID
List the subscribers (using their decryted keyids!)
Compare:
$ gpg2 -k 2A08A54D
pub rsa2048/2A08A54D 2016-02-08 [SC]
uid [ultimate] gnupg-devel <[email protected]> (mailing list)
sub rsa2048/ED2D0863 2016-02-08 [E]
sub rsa2/7C03B9E1 2016-02-08 [E]
sub rsa2/83BCEFE4 2016-02-08 [E]
sub rsa2/04A1E753 2016-02-08 [E]
sub rsa2/535EB487 2016-02-08 [E]
The above 2-bit RSA keys! These are the encrypted keys. Here are
the real subscribers:
$ gpg2 --mailing-list-subs 2A08A54D
D1B030E3
AA45C71F
94244910
95A0BEEA
4 subscribers.
To encrypt to a mailing list, just do: gpg2 -r ML-KEYID -e and a gnupg
with encrypted mailing list support will automatically encrypt to the
list of current subscribers.
|
