Annotation of pgp/contrib/md5sum/readme, revision 1.1.1.5

1.1.1.5 ! root        1: Instructions for the MD5SUM Utility
        !             2: -----------------------------------
        !             3: 
        !             4: This utility computes MD5 checksums of files, ignoring end-of-line
        !             5: conventions unless the -b (binary) flag is set.  
        !             6: 
        !             7: This utility can be used to check the integrity of any files.  For
        !             8: this discussion, we'll be checking the files in the PGP source code
        !             9: release.  For PGP version 2.6.3i, the file containing all the MD5
        !            10: message digests is called "pgp263i.md5", but for other versions of PGP,
        !            11: the filename will change to reflect the new version number.  
        !            12: 
        !            13: The file "pgp263i.md5" contains the signatures of all the files in the
        !            14: source.  If you are in the PGP base directory and run 
        !            15: 
        !            16:    md5sum -c contrib/md5sum/pgp263i.md5
        !            17: 
        !            18: you will get an error message if any files fail to match.  If all
        !            19: files match, nothing will be printed.
        !            20: 
        !            21: You need to borrow some files from the PGP sources to compile this
        !            22: utility (md5.c, md5.h, and possibly the getopt implementation);
        !            23: see the md5sum.c file for details.  On some platforms, you may have
        !            24: to compile md5.c with the -DHIGHFIRST flag, or the MD5 sums will be 
        !            25: wrong. Two makefiles, one for Unix and one for Amiga, are included.
        !            26: These should be a good starting point for tailoring makefiles on
        !            27: other systems.
        !            28: 
        !            29: The file pgp263i.md5 is signed by [email protected], so you can be
        !            30: reasonably sure it's correct.  It would be possible for a hard-working
        !            31: miscreant to fiddle with the distribution so all of this mutual checking
        !            32: would not show any errors, but it's not going to happen accidentally.
        !            33: And if you have a previous version of PGP that you trust, it's not going
        !            34: to happen at all.
        !            35: 
        !            36: The only other thing that's needed is a detached PGP signature of the
        !            37: files md5sum.c, md5.c and md5.h, and anyone with a previous trusted
        !            38: version of PGP can be sure that no tampering has occurred anywhere, and
        !            39: that's here:
        !            40: 
        !            41: md5sum.c:
        !            42: -----BEGIN PGP MESSAGE-----
        !            43: Version: 2.6.3i
        !            44: 
        !            45: iQCVAgUAMPZzGrCfd7bM70R9AQH7PQQAiyd/myRHDk8IrzpB/4sVO3Slj8tZc3dE
        !            46: 5Swfe3GkBpTyTvZYbqxwq1HQu5mAJbJsMbZD2s8D3BWKYAJZfrkNmutVKE6n9UVu
        !            47: eS2DXBPSalCZmQcv0UcHzbca9mExhgi4HGwy81kvUOAI6YWB22bYsk4DgciCRUx6
        !            48: 6wcNUMPqN+Q=
        !            49: =HUeq
        !            50: -----END PGP MESSAGE-----
        !            51: 
        !            52: md5.c:
        !            53: -----BEGIN PGP MESSAGE-----
        !            54: Version: 2.6.3i
        !            55: 
        !            56: iQCVAgUAMPZzOrCfd7bM70R9AQHYQgP/aPMSp1knVNWkw/D3AW+WtE/qJ88M7FYN
        !            57: +v9DZjwdNpCMETUFHBRqzL2gx+A9OXlCnIVf38fDlyHIdiJz1pOtYhataV9XtVp9
        !            58: iS+ayzB3Yv7dUrPhynXsKGjtD9YjQ0wgvuuFKqchq1B6Cn3yYkN4pwGhRvAXO8x1
        !            59: Vz/OU+Ywd4M=
        !            60: =bzeZ
        !            61: -----END PGP MESSAGE-----
        !            62: 
        !            63: md5.h:
        !            64: -----BEGIN PGP MESSAGE-----
        !            65: Version: 2.6.3i
        !            66: 
        !            67: iQCVAgUAMPZzS7Cfd7bM70R9AQH6EgQAqIlxNGYAq3Ynx8DdCeq32/2qZQoDdVHl
        !            68: BwEQIv05clQsI01VnVsh4cNig3cTV+wg99UklOhzgiATQc3vFumgFkEJkF7bII1S
        !            69: LZTNdBm561/029KIBv9dzMdArarNqAQQ6iJnaepVyNzC73xTyFCtEcTz4UFg+WV3
        !            70: nbw9gIGnx70=
        !            71: =1cCa
        !            72: -----END PGP MESSAGE-----
        !            73: 
        !            74: These signatures were generated by [email protected]. His key is
        !            75: supplied in the keys.asc file in the PGP distribution and is signed
        !            76: by various PGP developers, so you know that we are who we say we are,
        !            77: and if there are any trojan horses in the source, you know who put
        !            78: them there.  Isn't security fun?)
        !            79: --
        !            80:        -Colin <[email protected]>
        !            81:        Revised by Jeffrey I. Schiller <[email protected]>
        !            82:         Revised by Stale Schumacher <[email protected]>

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.