blob: aff39556c1ce6e8934db12695085925f81619be8 (
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
71
72
73
74
75
76
77
|
@c instguide.texi - Installation guide for GnuPG
@c Copyright (C) 2006 Free Software Foundation, Inc.
@c This is part of the GnuPG manual.
@c For copying conditions, see the file gnupg.texi.
@node Installation
@chapter A short installation guide.
Unfortunately the installation guide has not been finished in time.
Instead of delaying the release of GnuPG 2.0 even further, I decided to
release without that guide. The chapter on gpg-agent and gpgsm do
include brief information on how to set up the whole thing. Please
watch the GnuPG website for updates of the documentation. In the
meantime you may search the GnuPG mailing list archives or ask on the
gnupg-users mailing listsfor advise on how to solve problems or how to
get that whole thing up and running.
** Building the software
Building the software is decribed in the file @file{INSTALL}. Given
that you are already reading this documentation we can only give some
extra hints
To comply with the rules on GNU systems you should have build time
configured @command{gnupg} using:
@example
./configure --sysconfdir=/etc --localstatedir=/var
@end example
This is to make sure that system wide configuration files are searched
in the directory @file{/etc/gnupg} and variable data below @file{/var};
the default would be to also install them below @file{/usr/local} where
the binaries get installed. If you selected to use the
@option{--prefix=/} you obviously don't need those option as they are
the default then.
** Notes on setting a root CA key to trusted
X.509 is based on a hierarchical key infrastructure. At the root of the
tree a trusted anchor (root certificate) is required. There are usually
no other means of verifying whether this root certificate is trustworthy
than looking it up in a list. GnuPG uses a file (@file{trustlist.txt})
to keep track of all root certificates it knows about. There are 3 ways
to get certificates into this list:
@itemize
@item
Use the list which comes with GnuPG. However this list only
contains a few root certificates. Most installations will need more.
@item
Let @command{gpgsm} ask you whether you want to insert a new root
certificate. This feature is enabled by default; you may disable it
using the option @option{no-allow-mark-trusted} into
@file{gpg-agent.conf}.
@item
Manually maintain the list of trusted root certificates. For a multi
user installation this can be done once for all users on a machine.
Specific changes on a per-user base are also possible.
@end itemize
@c decribe how to maintain trustlist.txt and /etc/gnupg/trustlist.txt.
@c ** How to get the ssh support running
@c
@c XXX How to use the ssh support.
@c @section Installation Overview
@c
@c XXXX
|
