![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to setup.doc CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [PGP] / pgp / src|
Return to setup.doc CVS log | Up to [PGP] / pgp / src |
1.1 root 1: Pretty Good Privacy version 2.0 - Installation Guide
2:
3:
4:
5: How to Install PGP
6: ==================
7:
8: The first question is, what platform are you on?
9:
10: PGP 2.0 runs on several varieties of Unix, MS-DOS, VAX VMS, Ataris,
11: Amigas, and possibly other operating systems. Naturally, installation
12: instructions differ depending on your hardware. Separate instructions
13: are provided here for MSDOS and Unix.
14:
15: No matter what the machine you are on, though, do this...
16:
17: STEP 1:
18: READ THE DOCUMENTATION. At least read Volume I of the PGP User's
19: Guide. Cryptography software is easy to misuse, and if you don't use
20: it properly much of the security you could gain by using it will be
21: lost! You might also be unfamiliar with the concepts behind public
22: key cryptography; the manual explains these ideas. Even if you are
23: already familiar with Public Key Cryptography, it is important that
24: you understand the various security issues associated with using
25: PGP. It may not be important to read the fine print on a box of
26: breakfast cereal, but it may be crucial to read the label of a
27: prescription drug. Cryptography software is like pharmaceuticals--
28: so read the manual!
29:
30: See the section below for your system's particular installation
31: instructions.
32:
33: If you do not have any of these systems, you will either have to port
34: the sources to your machine or find someone who has already done so.
35:
36: ######################################################################
37: For MSDOS:
38:
39: PGP is distributed in a compressed archive format, which keeps all
40: the relevant files grouped together, and also saves disk space and
41: transmission time.
42:
43: The current version, 2.0, is archived with the PKZIP utility, and the
44: PGP executable binary release system is in a file named PGP20.ZIP.
45: This contains the executable program, the user documentation, and a
46: few keys and signatures. There is also a second file available
47: containing the C and assembly source code, called PGP20SRC.ZIP; unless
48: you are a programmer interested in cryptography, it is probably of
49: little interest to you. It may or may not be available from the
50: source from which you get PGP20.ZIP; if not, and you want it, see the
51: Licensing and Distribution section of the PGP User's Guide.
52:
53: You will need PKUNZIP version 1.1 or later to uncompress and split
54: the PGP20.ZIP archive file into individual files. PKUNZIP is
55: shareware and is widely available on MSDOS machines.
56:
57: Create a directory for the PGP files. For this description, let's
58: use the directory C:\PGP as an example, but you should substitute
59: your own disk and directory name if you use something different.
60: Type these commands to make the new directory:
61:
62: c:
63: md \pgp
64: cd \pgp
65:
66: Uncompress the distribution file PGP20.ZIP to the directory. For
67: this example, we will assume the file is on floppy drive A - if not,
68: substitute your own file location.
69:
70: pkunzip a:pgp20
71:
72:
73: Setting the Environment
74: -----------------------
75:
76: Next, you can set an MSDOS "environment variable" to let PGP know
77: where to find its special files, in case you use it from other than
78: the default PGP directory. Use your favorite text editor to add the
79: following lines to your AUTOEXEC.BAT file (usually on your C: drive):
80:
81: SET PGPPATH=C:\PGP
82: SET PATH=C:\PGP;%PATH%
83:
84: Substitute your own directory name if different from "C:\PGP".
85:
86: Another environmental variable you should set in MSDOS is "TZ", which
87: tells MSDOS what time zone you are in, which helps PGP create GMT
88: timestamps for its keys and signatures. If you properly define TZ in
89: AUTOEXEC.BAT, then MSDOS gives you good GMT timestamps, and will
90: handle daylight savings time adjustments for you. Here are some
91: sample lines to insert into AUTOEXEC.BAT, depending on your time
92: zone:
93:
94: For Colorado: SET TZ = MST7MDT
95: For Arizona: SET TZ = MST7
96: (Arizona never uses daylight savings time)
97: For Chicago: SET TZ = CST6CDT
98: For New York: SET TZ = EST5EDT
99: For London: SET TZ = GMT0BST
100: For Amsterdam: SET TZ = MET-1DST
101:
102: Now reboot your system to run AUTOEXEC.BAT and set up PGPPATH and TZ
103: for you.
104:
105:
106:
107: Generating Your First Key
108: -------------------------
109:
110: One of the first things you will want to do to really use PGP (other
111: than to test itself) is to generate your own key. This is described
112: in more detail in the "RSA Key Generation" section of PGP User's
113: Guide. Remember that your key becomes something like your written
114: signature or your bank card code number or even a house key - keep it
115: secret and keep it secure! Use a good, unguessable pass phrase and
116: remember it. Right after you generate a key, put it on your key
117: rings and copy your secret keyring (SECRING.PGP) to a blank floppy
118: and write protect the floppy.
119:
120: After you generate your own key pair, you can add a few more public
121: keys to your key ring. A collection of sample public keys is
122: provided with the release in the file KEYS.ASC. To add them to your
123: public key ring, see the PGP User's Guide, in the section on adding
124: keys to your key ring.
125:
126:
127: ######################################################################
128: For UNIX:
129:
130: You likely will have to compile PGP for your system; to do this, first
131: make sure the unpacked files are in the correct unix textfile format
132: (the files in pgp20src.zip are in MSDOS CRLF format, so for unix you
133: must unpack with "unzip -a"). Then copy the file "makefile.unx" in the
134: distribution to "Makefile".
135:
136: If you don't have an ANSI C compiler you will need the unproto package
137: written by Wietse Venema. unproto was posted on comp.sources.misc and
138: can be obtained from the various sites that archive this newsgroup
139: (volume 23: v23i012 and v23i013) or ftp.win.tue.nl file:
140: /pub/programming/unproto4.shar.Z Read the file README in the unproto
141: distribution for instructions on how to use unproto. The unix makefile
142: for pgp (makefile.unx) contains a few targets for compliling with
143: unproto, these assume you have unpacked unproto in a subdirectory
144: "unproto" in the pgp "src" directory.
145:
146:
147: Then...
148:
149: type:
150: "make sungcc" for Sun with GNU gcc
151: "make suncc" for Sun with cc and unproto
152: "make sysv_386" for SVR4 386 with asm primitives
153: "make x286" for XENIX/286 with asm primitives and unproto
154: "make ultrix" for DEC 4.2BSD Ultrix with gcc
155: "make rs6000" for RS6000 AIX
156:
157: If your system doesn't have a target in makefile.unx you will have to
158: edit the makefile, make sure you compile for the correct byte order for
159: your system: define HIGHFIRST if your system is big-endian (eg. Motorola
160: 68030).
161:
162: If all goes well, you will end up with an executable file called "pgp".
163:
164: Before you install pgp, run these tests:
165: (do not create your real public key yet, this is just for testing pgp)
166:
167: - create a public/secret key pair (enter "test" as userid/password):
168: pgp -kg
169:
170: - add the sample keys from the file "keys.asc" to the public keyring:
171: pgp -ka keys.asc
172: pgp will ask if you want to sign the keys you are adding, answer yes
173: for at least one key.
174:
175: - do a keyring check:
176: pgp -kc
177:
178: - encrypt pgpdoc1.txt:
179: pgp -e pgpdoc1.txt test -o testfile.pgp
180:
181: - decrypt this file:
182: pgp testfile.pgp
183:
184: this should produce the file "testfile" compare this file with pgpdoc1.txt
185:
186: If everything went well, install pgp in a bin directory.
187:
188: Place the documentation, pgpdoc1.txt and pgpdoc2.txt somewhere where
189: you can reasonably read it; since it's for you, not the software, the
190: location doesn't really matter.
191:
192: Place the man page (pgp.1) in an appropriate spot. If you don't know
193: anything about how man pages work, you can make the man page look
194: human readable yourself by typing "nroff -man pgp.1 >pgp.man" and
195: reading "pgp.man".
196:
197: Create a subdirectory somewhere in your home directory hierarchy to
198: hold your public and private key rings and anything else pgp might
199: need (like the language.txt file). You must set the environment
200: variable "PGPPATH" to point to this place before you use the system.
201: Copy the files "language.txt", "config.txt", and the ".hlp" files from
202: the distribution into this subdirectory.
203:
204: IMPORTANT: THIS DIRECTORY CANNOT BE SHARED! IT WILL CONTAIN YOUR
205: PERSONAL PRIVATE KEYS!
206:
207: IMPORTANT: PLEASE READ THE SECTIONS IN THE MAN PAGE AND MANUAL ABOUT
208: VULNERABILITIES BEFORE EVEN THINKING ABOUT USING THIS SOFTWARE ON A
209: MULTI-USER MACHINE!!!!
210:
211: Now, if you haven't done so yet, GO READ THE MANUAL.
212:
213:
214: ######################################################################
215: For VMS:
216:
217: Read the file readme.vms in the vms subdirectory
218:
219: ######################################################################
220: For Amiga:
221:
222: [This space intentionally left blank]
223:
224: ######################################################################
225: For Atari:
226:
227: [This space intentionally left blank]
228: ######################################################################
229:
230:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.