--- pgp/doc/pgpdoc1.txt 2018/04/24 16:43:58 1.1.1.5 +++ pgp/doc/pgpdoc1.txt 2018/04/24 16:44:56 1.1.1.6 @@ -1,6 +1,5 @@ - Phil's Pretty Good Software Presents @@ -17,10 +16,10 @@ Volume I: Essential Topics -------------------------- by Philip Zimmermann - Revised 31 August 94 + Revised 11 October 94 - PGP Version 2.6.1 - 30 Aug 94 + PGP Version 2.6.2 - 11 Oct 94 Software by Philip Zimmermann, and many others. @@ -75,7 +74,7 @@ How to Use PGP Advanced Topics Sending Ciphertext Through E-mail Channels: Radix-64 Format Environmental Variable for Path Name - Setting Configuration Parameters: CONFIG.TXT + Setting Parameters in the PGP Configuration File Vulnerabilities Beware of Snake Oil Notice to Macintosh Users @@ -365,24 +364,28 @@ release. If you already have an earlier version of PGP, you should rename it or delete it, to avoid name conflicts with the new PGP. -To install PGP on your MSDOS system, you just have to copy the -compressed archive PGPxx.ZIP file into a suitable directory on your -hard disk (like C:\PGP), and decompress it with PKUNZIP. For best -results, you will also modify your AUTOEXEC.BAT file, as described -elsewhere in this manual, but you can do that later, after you've -played with PGP a bit and read more of this manual. If you haven't -run PGP before, the first step after installation (and reading this -manual) is to run the PGP key generation command "pgp -kg". +For full details on how to install PGP, see the separate PGP +Installation Guide, in the file SETUP.DOC included with this release +package. It fully describes how to set up the PGP directory and your +AUTOEXEC.BAT file and how to use PKUNZIP to install it. We will just +briefly summarize the installation instructions here, in case you are +too impatient to read the more detailed installation manual right now. + +To install PGP on your MSDOS system, you have to copy the compressed +archive PGPxx.ZIP file into a suitable directory on your hard disk +(like C:\PGP), and decompress it with PKUNZIP. For best results, you +should also modify your AUTOEXEC.BAT file, as described elsewhere in +this manual, but you can do that later, after you've played with PGP +a bit and read more of this manual. If you haven't run PGP before, +the first step after installation (and reading this manual) is to +make a pair of keys for yourself by running the PGP key generation +command "pgp -kg". Read the "RSA Key Generation" section of the +manual first. Installing on Unix and VAX/VMS is generally similar to installing on MSDOS, but you may have to compile the source code first. A Unix makefile is provided with the source release for this purpose. -For further details on installation, see the separate PGP -Installation Guide, in the file SETUP.DOC included with this -release. It fully describes how to set up the PGP directory and your -AUTOEXEC.BAT file and how to use PKUNZIP to install it. - How to Use PGP @@ -675,9 +678,10 @@ exposing it by storing it on a remote ti on your own personal computer. If PGP complains about not being able to find the PGP User's Guide on -your computer, and refuses to generate a key pair without it, read -the explanation of the NOMANUAL parameter in the section "Setting -Configuration Parameters" in the Special Topics volume. +your computer, and refuses to generate a key pair without it, don't +panic. Just read the explanation of the NOMANUAL parameter in the +section "Setting Configuration Parameters" in the Special Topics +volume of the PGP User's Guide. Adding a Key to Your Key Ring @@ -1216,7 +1220,7 @@ To produce a ciphertext file in ASCII ra pgp -esa message.txt her_userid This example produces a ciphertext file called "message.asc" that -contains data in a PEM-like ASCII radix-64 format. This file can be +contains data in a MIME-like ASCII radix-64 format. This file can be easily uploaded into a text editor through 7-bit channels for transmission as normal E-mail on Internet or any other E-mail network. @@ -1234,8 +1238,8 @@ ciphertext file in binary form. The fin plaintext form, just as it was in the original file "message.txt". Most Internet E-mail facilities prohibit sending messages that are -more than 50000 bytes long. Longer messages must be broken into -smaller chunks that can be mailed separately. If your encrypted +more than 50000 or 65000 bytes long. Longer messages must be broken +into smaller chunks that can be mailed separately. If your encrypted message is very large, and you requested radix-64 format, PGP automatically breaks it up into chunks that are each small enough to send via E-mail. The chunks are put into files named with extensions @@ -1265,8 +1269,16 @@ the plaintext message. This makes it po read the signed message with human eyes, without the aid of PGP. Of course, PGP is still needed to actually check the signature. For further information on this feature, see the explanation of the -CLEARSIG parameter in the section "Setting Configuration Parameters: -CONFIG.TXT" in the Special Topics volume. +CLEARSIG parameter in the section "Setting Configuration Parameters" +in the Special Topics volume. + +Sometimes you may want to send a binary data file through an E-mail +channel without encrypting or signing it with PGP. Some people use +the Unix uuencode utility for that purpose. PGP can also be used for +that purpose, by simply using the -a option alone, and it does a +better job than the uuencode utility. For further details, see the +section on "Using PGP as a Better Uuencode" in the Special Topics +volume. Environmental Variable for Path Name @@ -1275,10 +1287,11 @@ Environmental Variable for Path Name PGP uses several special files for its purposes, such as your standard key ring files "pubring.pgp" and "secring.pgp", the random number seed file "randseed.bin", the PGP configuration file -"config.txt", and the foreign language string translation file -"language.txt". These special files can be kept in any directory, by -setting the environmental variable "PGPPATH" to the desired pathname. -For example, on MSDOS, the shell command: +"config.txt" (or "pgp.ini", or ".pgprc"), and the foreign language +string translation file "language.txt". These special files can be +kept in any directory, by setting the environmental variable +"PGPPATH" to the desired pathname. For example, on MSDOS, the shell +command: SET PGPPATH=C:\PGP @@ -1291,16 +1304,20 @@ files are assumed to be in the current d -Setting Configuration Parameters: CONFIG.TXT --------------------------------------------- +Setting Parameters in the PGP Configuration File +------------------------------------------------ PGP has a number of user-settable parameters that can be defined in a -special configuration text file called "config.txt", in the directory -pointed to by the shell environmental variable PGPPATH. Having a -configuration file enables the user to define various flags and -parameters for PGP without the burden of having to always define +special PGP configuration text file called "config.txt", in the +directory pointed to by the shell environmental variable PGPPATH. +Having a configuration file enables the user to define various flags +and parameters for PGP without the burden of having to always define these parameters in the PGP command line. +In the interest of complying with local operating system file naming +conventions, for Unix systems this configuration file may also be +named ".pgprc", and on MSDOS systems it may also be named "pgp.ini". + With these configuration parameters, for example, you can control where PGP stores its temporary scratch files, or you can select what foreign language PGP will use to display its diagnostics messages and @@ -1675,13 +1692,13 @@ controls, see the "Legal Issues" section Volume II: Special Topics". PGP uses a public key algorithm claimed by U.S. patent #4,405,829. -The exclusive licensing rights to this patent are held by a -California company called Public Key Partners, and you may be -infringing the patent if you use PGP in the USA without a license. -These issues are detailed in the Volume II manual, and in the RSAREF -license that comes with the freeware version of PGP. PKP has licensed -others to practice the patent, including a company known as ViaCrypt, -in Phoenix, Arizona. ViaCrypt sells a fully licensed version of PGP. +The exclusive licensing rights to this patent are held by a company +called Public Key Partners (PKP), and you may be infringing the +patent if you use PGP in the USA without a license. These issues are +detailed in the Volume II manual, and in the RSAREF license that +comes with the freeware version of PGP. PKP has licensed others to +practice the patent, including a company known as ViaCrypt, in +Phoenix, Arizona. ViaCrypt sells a fully licensed version of PGP. ViaCrypt may be reached at 602-944-0773. PGP is "guerrilla" freeware, and I don't mind if you distribute it