|
|
1.1 ! root 1: Changes to PGP 2.6: ! 2: ! 3: This version of PGP uses a version of RSAREF provided to MIT by RSA Data ! 4: Security for use in PGP. This version is legal within the U.S. See the ! 5: enclosed RSAREF license for full details. Basically this is a ! 6: non-commercial release. If you want to use it in a commercial or ! 7: governmental setting, talk to ViaCrypt (2014 West Peoria Avenue, ! 8: Phoenix, Arizona 85029, +1 602 944-0773). ! 9: ! 10: While PGP version 2.5 used RSAREF version 2.0, PGP 2.6 uses RSAREF ! 11: version 1. This change was made in consultation with RSA Data ! 12: Security, which is currently revising its version 2.0 distribution. ! 13: The version of RSAREF included with this distribution is RSAREF ! 14: version 1, not version 2.0. ! 15: ! 16: PGP 2.6 will read messages, signatures and keys created with versions of ! 17: PGP post 2.2. (i.e., 2.3, 2.3a, 2.4 and 2.5). However after 9/1/94 Version ! 18: 2.6 will create messages which contain a version number of "3" in signatues, ! 19: messages and keys (see pgformat.doc for details). PGP2.6 will be able to ! 20: read these signatures, messages and keys, but prior versions will not. ! 21: ! 22: Versions prior to 2.6 would not permit a new signature to be added to a key ! 23: if there was an already existing signature from the same signer. Starting ! 24: with version 2.6 newer signatures will override older ones *as long as the ! 25: newer signature verifies*. This change is important because many keys have ! 26: signatures on them that were created by PGP version 2.2 or earlier. These ! 27: signatures can not be verified by PGP 2.5 or higher. Owners of keys with ! 28: these obsolete signatures should attempt to gather new signatures and ! 29: add them to their key. ! 30: ! 31: Significant changes were also made for version 2.5. Because version 2.6 is ! 32: coming out very soon after 2.5 (which was only really a beta test version) ! 33: readers are encouraged to read the file "newfor25.doc" as well as this file.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.