--- pgp/doc/setup.doc 2018/04/24 16:43:58 1.1.1.5 +++ pgp/doc/setup.doc 2018/04/24 16:44:57 1.1.1.6 @@ -1,6 +1,6 @@ -----BEGIN PGP SIGNED MESSAGE----- - Pretty Good Privacy Version 2.6.1 + Pretty Good Privacy Version 2.6.2 Installation Guide by Perry Metzger, Colin Plumb, Derek Atkins, @@ -11,11 +11,12 @@ How to Install PGP The first question is, what platform are you on? -The base PGP 2.6.1 distribution runs on several varieties of Unix, -MS-DOS and VAX VMS (though we haven't compiled it ourselves there yet). -Ports can be expected shortly to the Atari, Amiga, and possibly other -systems. Naturally, installation instructions differ depending on your -hardware. Separate instructions are provided here for MSDOS and Unix. +The base PGP 2.6.2 distribution runs on several varieties of Unix, +MS-DOS, OS/2 and VAX VMS (though we haven't compiled it ourselves there +yet). Ports can be expected shortly to the Atari, Amiga, and possibly +other systems. Naturally, installation instructions differ depending on +your hardware. Separate instructions are provided here for MSDOS and +Unix. See the section below for your system's particular installation instructions. @@ -24,26 +25,39 @@ If you do not have any of these syste the sources to your machine or find someone who has already done so. ######################################################################## -For MSDOS: + +For MSDOS Installation +====================== PGP is distributed in a compressed archive format, which keeps all the relevant files grouped together, and also saves disk space and transmission time. -The current version, 2.6.1, is archived with the ZIP utility, and the -PGP executable binary release system is in a file named PGP261.ZIP. +The current version, 2.6.2, is archived with the ZIP utility, and the +PGP executable binary release system is in a file named PGP262.ZIP. This contains the executable program, the user documentation, the RSAREF -license, and a few keys and signatures. There is also a second file -available containing the C and assembly source code, called PGP261S.ZIP. +license, and a few keys and signatures. There is also a second file +available containing the C and assembly source code, called PGP262S.ZIP. If you are a programmer, this may be of interest to you. This should be -available from the same source from which you got PGP261.ZIP. If not, -and you want it, see the Licensing and Distribution section of the PGP -User's Guide. +available from the same source from which you got PGP262.ZIP. If not, +and you want it, see the Licensing and Distribution section of the PGP +User's Guide. There is also an archive PGP262DC.ZIP, which is just the +documentation, if you just want to see a description of PGP or have +misplaced the manual. -You will need PKUNZIP version 1.1 or later to uncompress and split the -PGP26.ZIP archive file into individual files. PKUNZIP is shareware and +You will need PKUNZIP version 2.04g or later to uncompress and split the +PGP262.ZIP archive file into individual files. PKUNZIP is shareware and is widely available on MSDOS machines. +Each of the ZIP files is actually two nested zip files. Inside +PGP262.ZIP is PGP262I.ZIP, which contains most of the files, and +PGP262I.ASC, which is a PGP signature on PGP262I.ASC. If you have a +previous version of PGP, you can use it to check the signature to see +that the distribution has not been tampered with. Since a PGP signature +protects every last bit in a file from change, a BBS adding an +advertising blurb or recompressing the archive would cause PGP to report +tampering. Thus, only the inner ZIP file is signed. + Create a directory for the PGP files. For this description, let's use the directory C:\PGP26 as an example, but you should substitute your own disk and directory name if you use something different. Type these @@ -53,24 +67,25 @@ commands to make the new directory: md \pgp26 cd \pgp26 -Uncompress the distribution file PGP261.ZIP to the directory. For this +Uncompress the distribution file PGP262.ZIP to the directory. For this example, we will assume the file is on floppy drive A - if not, substitute your own file location. - pkunzip -d a:pgp261 + pkunzip -d a:pgp262 -This will create the file PGP261I.ZIP and PGP261I.ASC. Unzip -PGP261I.ZIP with the command: +This will create the file PGP262I.ZIP and PGP262I.ASC. Unzip +PGP262I.ZIP with the command: - pkunzip -d pgp261i + pkunzip -d pgp262i If you omit the -d flag, all the files in the doc subdirectory will be deposited in the pgp directory. This merely causes clutter. -Keep the PGP261I.ZIP file around. Once you have PGP working you can use -PGP261I.ASC to verify the digital signature on PGP261I.ZIP. It should +Keep the PGP262I.ZIP file around. Once you have PGP working you can use +PGP262I.ASC to verify the digital signature on PGP262I.ZIP. It should come from Jeffrey I. Schiller (whose key is included in keys.asc). + Setting the Environment ----------------------- @@ -84,11 +99,11 @@ following lines to your AUTOEXEC.BAT fil Substitute your own directory name if different from "C:\PGP26". -The CONFIG.TXT file contains various preferences. You can change the -language PGP operates in, and the character set it uses. The IBM PC's -default character set, "Code Page 850" will be used if the line "charset -= cp850" appears in the config.txt file. You probably want to add that -line. +The CONFIG.TXT file contains various user-defined preferences for PGP. +For example, you can specify which of your secret keys to implicitly +select for creating digital signatures. See the manual for details on +how to fine-tune your PGP configuration file. The default values in +that file are good enough to get you started. Another environmental variable you should set in MSDOS is "TZ", which tells MSDOS what time zone you are in, which helps PGP create GMT @@ -145,11 +160,11 @@ Now that you have PGP up and running an you can now verify the integrity of the original distribution. To do this type: - pgp pgp261i.asc + pgp pgp262i.asc -It will inform you that pgp261i.asc contains a signature but no text. +It will inform you that pgp262i.asc contains a signature but no text. It may then ask you to provide the name of the file that it applies to. -Type in "pgp261i.zip", the internal ZIP file. +Type in "pgp262i.zip", the internal ZIP file. PGP should tell you that it has a Good Signature from: @@ -178,20 +193,20 @@ For UNIX: You likely will have to compile PGP for your system; to do this, first make sure the unpacked files are in the correct unix textfile format -(the files in pgp261s.zip are in MSDOS CRLF format, so for Unix you must -unpack with "unzip -a"; the tar files pgp261s.tar.Z and pgp261s.tar.gz +(the files in pgp262s.zip are in MSDOS CRLF format, so for Unix you must +unpack with "unzip -a"; the tar files pgp262s.tar.Z and pgp262s.tar.gz use normal Unix line feed conventions). -You will need the RSAREF package written by RSA Data Security. It is -included with the PGP 2.6.1 distribution from MIT. Use this version as -it has been edited for the larger key sizes needed by PGP 2.6.1 as well -as to improve performance. +You will need the RSAREF package written by RSA Data Security. It is +included with the current PGP distribution from MIT. Use this version +as it has been edited for the larger key sizes needed by PGP 2.6.2 as +well as to improve performance. -When you untar pgp261s.tar (either compression format) you will find -that it contains 5 files. pgp261si.tar contains all non-binary files for +When you untar pgp262s.tar (either compression format) you will find +that it contains 5 files. pgp262si.tar contains all non-binary files for PGP including all source code. This tar archive has been created -assuming that you will untar it directly into your PGP 2.6.1 "build" -directory. pgp261si.asc is a detached digital signature of pgp261si.tar +assuming that you will untar it directly into your PGP 2.6.2 "build" +directory. pgp262si.asc is a detached digital signature of pgp262si.tar (which you can verify after you have PGP operating, see the section above titled "Verifying the PGP Distribution"). rsaref.tar contains the source code for the RSAREF distribution. You should also untar it from @@ -241,13 +256,13 @@ file. If you successfully create a target rule for a new platform, please send the patches to pgp-bugs@mit.edu, so it can be added to the next release. -Note: PGP 2.6.1 requires the function memmove. Not all machines have -this in the standard C library. There is an implementation of memmove -included with this distribution. If you find that your platform -requires memmove, but the makefile rule for your platform does not -include memmove (look at the sun4gcc or sun386i rules for an example of -how to include it), please send mail to pgp-bugs@mit.edu, so we can -correct the problem. +Note: PGP requires the function memmove. Not all machines have this in +the standard C library. There is an implementation of memmove included +with this distribution. If you find that your platform requires +memmove, but the makefile rule for your platform does not include +memmove (look at the sun4gcc or sun386i rules for an example of how to +include it), please send mail to pgp-bugs@mit.edu, so we can correct the +problem. If you have any problems, bugs, patches, etc., please send mail to pgp-bugs@mit.edu! @@ -321,16 +336,16 @@ Now, if you haven't done so yet, GO READ ######################################################################## For VMS: - PGP/VMS Version 2.6.1 + PGP/VMS Version 2.6.2 --------------------- ***THIS MAY OR MAY NOT WORK***. The pgp26/vmsbuild contains support files for building a VMS version of -PGP 2.6.1. We at MIT have not tested this code out, but it should work +PGP 2.6.2. We at MIT have not tested this code out, but it should work without too much effort. See the file: vmsbuild/000read.me. -In particular, PGP 2.6.1 needs to be linked with the RSAREF library. +In particular, PGP needs to be linked with the RSAREF library. David North has provided a build file "vmsbuild/rsabuild.com" that should help in building RSAREF. @@ -339,12 +354,13 @@ that PGP can now look for support files default (PGP_SYSTEM_DIR, defined in fileio.h) is PGP$LIBRARY:, but you can change that if you like. + -----BEGIN PGP SIGNATURE----- -Version: 2.6.1 +Version: 2.6.2 -iQCVAwUBLmuzYcUtR20Nv5BtAQEwnwP9FqPOE9aEet4+qtTXTW5YNrpqwvQxF0/h -ytH2WYMgA0HFRIZN9Crx5SQBX8syqaEZs0GPxOoLPVPCHVV8G3Dg3L8f72kwRAC+ -J2Z+XBt49RwwRIWm+MmWfG5IwS4OlAXTe+IDxgdViXuDDNVoWysGaWJSW+hv+yry -xU9pY5AYBKc= -=8s1o +iQCVAwUBLqmXwsUtR20Nv5BtAQG+rQP+KBJzh22axMqNymQtN55iU+znyJwnaTge +buI7mpZnjUAYBZvOHhxVtUg/5v4PgDISrDnTkne6EZdDNEH5nP9AB8YDOChourKg +drUlhn7NsEyToqDF42rX53kq0kc8P7CWilQvTfti6i8bAGWLAN9dwdq0iwFxRz8I +G8Cql4kIbhA= +=0JzK -----END PGP SIGNATURE-----