blob: e22285a198740beec1cab090e6e2f53b13375cf7 (
plain) (
blame)
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
|
SPELL=sorcery-pubkeys
VERSION=1.6
LICENSE=GPL
WEB_SITE=http://www.sourcemage.org/
BUILD_API=2
ENTERED=20041222
SECURITY_PATCH=1
SHORT="Sorcery public key installer"
cat << EOF
This installs the sorcery public keys into /etc/sorcery/local/
The keys are generated with:
gpg --no-default-keyring --keyring ./sorcery-devel.gpg --import
paste in public key
press ctrl-d
or:
gpg --no-default-keyring --keyring ./sorcery-devel.gpg --secret-keyring ./sorcery-devel-private.gpg --gen-key
There are currently these keys:
sorcery-devel.gpg
sorcery-test.gpg
sorcery-stable.gpg
grimoire-devel.gpg
grimoire-test.gpg
grimoire-hardened.gpg
grimoire-stable-rc.gpg
grimoire-stable.gpg
grimoire-games.gpg
grimoire-z-rejected.gpg
They are used during sorcery update (sorcery) and scribe update
(grimoire) to verify downloads.
The private keys for sorcery-test and sorcery-stable are kept with the
sorcery team lead.
The private key for grimoire-stable is kept with the stable grimoire
maintainer and the security team lead.
The private key for sorcery-devel is used to sign sorcery-devel
snapshots.
The private keys for grimoire-{devel,test,games,z-rejected} are used to
sign their respective snapshots.
EOF
|
