|
|
1.1 ! root 1: Pretty Good Privacy version 2.0 - READ ME FIRST ! 2: ! 3: ! 4: You are looking at the README file for PGP release 2.0. PGP, short for ! 5: Pretty Good Privacy, is a public key encryption package; with it, you ! 6: can secure messages you transmit against unauthorized reading and ! 7: digitally sign them so that people receiving them can be sure they ! 8: come from you. ! 9: ! 10: The files pgpdoc1.txt and pgpdoc2.txt contain documentation for the ! 11: system. ! 12: ! 13: Before using PGP, PLEASE READ THE DOCUMENTATION. This tends to get ! 14: neglected with most computer software, but cryptography software is ! 15: easy to misuse, and if you don't use it properly much of the security ! 16: you could gain by using it will be lost! You might also be unfamiliar ! 17: with the concepts behind public key cryptography; the manual explains ! 18: these ideas. Even if you are already familiar with public key ! 19: cryptography, it is important that you understand the various security ! 20: issues associated with using PGP. ! 21: ! 22: The file SETUP.DOC contains information on how to install PGP on your ! 23: system; this document is broken up into several sections, each dealing ! 24: with a different operating system: PGP is known to run on MS-DOS, ! 25: UNIX, and VMS. Part of the information in SETUP.DOC might make more ! 26: sense if you have already read the manuals. ! 27: ! 28: PGP 2.0, which was released on September 3, 1992, will likely be ! 29: followed by updated versions within a few months of the release date. ! 30: Bugs will likely be found and fixed, this being a new major release of ! 31: the software, and we will try to get these fixes out to the public as ! 32: soon as possible. ! 33: ! 34: Given this, if you have received PGP 2.0 substantially after the ! 35: initial release date, you may want to check around for a more recent ! 36: release. If there is a more recent release, please acquire it, and ! 37: please get the place you got PGP 2.0 from to update their release, ! 38: too. ! 39: ! 40: ! 41: MANIFEST for PGP 2.0 MSDOS executable release ! 42: --------------------------------------------- ! 43: ! 44: Here is a list of files included in the PGP 2.0 MSDOS executable release ! 45: file PGP20.ZIP... ! 46: ! 47: README.DOC - This file you are reading ! 48: SETUP.DOC - Installation guide ! 49: PGP.EXE - PGP executable program ! 50: CONFIG.TXT - User configuration parameter file for PGP ! 51: LANGUAGE.TXT - Sample language file for French and Spanish ! 52: PGP.HLP - Online help file for PGP ! 53: ES.HLP - Online help file in Spanish ! 54: FR.HLP - Online help file in French ! 55: PGPDOC1.DOC - PGP User's Guide, Vol I: Essential Topics ! 56: PGPDOC2.DOC - PGP User's Guide, Vol II: Special Topics ! 57: KEYS.ASC - Sample public keys to add to your keyring ! 58: PGPSIG.ASC - Detached signature of PGP.EXE, to detect viruses ! 59: ! 60: ! 61: For Clinical Paranoia Sufferers Only ! 62: ------------------------------------ ! 63: ! 64: It is always possible that the PGP you have received has been tampered ! 65: with in some way. This is a risk because PGP is used as a system to ! 66: assure security, so those wishing to breach your security could likely ! 67: do it by making sure that your copy of PGP has been tampered with. Of ! 68: course, if you receive PGP in a binary distribution, it makes sense to ! 69: check it for viruses, and if you receive PGP as source code, looking ! 70: for signs of obvious tampering might be a good idea. However, it is ! 71: very difficult to actually determine if the code has no subtle bugs ! 72: that have been introduced and that the executable you are using has ! 73: not been tampered with in any way. If you are a really paranoid ! 74: person, try getting a cryptographically signed copy of the software ! 75: from someone you trust to have a good copy. It would also likely be ! 76: good for you to read the sections of the manual on "Vulnerabilities", ! 77: which you should have read anyway since you have read the ! 78: documentation already, haven't you? ! 79: ! 80:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.