![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to readme CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [PGP] / pgp / contrib / md5sum|
Return to readme CVS log | Up to [PGP] / pgp / contrib / md5sum |
1.1.1.4 ! root 1: Instructions for the MD5SUM Utility ! 2: ----------------------------------- ! 3: 1.1 root 4: This utility computes MD5 checksums of files, ignoring end-of-line 1.1.1.4 ! root 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.2, the file containing all the MD5 ! 10: message digests is called "pgp262.md5", but for other versions of PGP, ! 11: the filename will change to reflect the new version number. ! 12: ! 13: The file "pgp262.md5" contains the signatures of all the files in the ! 14: source. If you are in the source directory and run ! 15: ! 16: md5sum -c ../contrib/md5sum/pgp262.md5 ! 17: 1.1.1.3 root 18: you will get an error message if any files fail to match. If all 19: files match, nothing will be printed. 1.1 root 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); 1.1.1.4 ! root 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. 1.1 root 26: 1.1.1.4 ! root 27: The file pgp262.md5 is signed by [email protected], so you can be 1.1 root 28: reasonably sure it's correct. It would be possible for a hard-working 29: miscreant to fiddle with the distribution so all of this mutual checking 30: would not show any errors, but it's not going to happen accidentally. 31: And if you have a previous version of PGP that you trust, it's not going 32: to happen at all. 33: 34: The only other thing that's needed is a detached PGP signature of the 1.1.1.2 root 35: files md5sum.c, md5.c and md5.h, and anyone with a previous trusted 36: version of PGP can be sure that no tampering has occurred anywhere, and 37: that's here: 1.1 root 38: 1.1.1.2 root 39: md5sum.c: 1.1 root 40: -----BEGIN PGP MESSAGE----- 1.1.1.3 root 41: Version: 2.6.1 1.1 root 42: 1.1.1.3 root 43: iQCVAwUBLmkvh8UtR20Nv5BtAQGt6AP/S41H9gw7rfifG7W6ZlMviV4VVeov1C54 44: wkS/rjG3+tCm2Gcixfcx7iPb6wIbg5IqWtjbuPd2xvpyLn8MrN3E4Llak7tOBVg7 45: insTxrqzjmSNCxVPe3X5+QqnOY7TlI6qIjhZ74Wb9gKiQxKn3f5yjKzJKvpv20a1 46: ngI7v5BADKQ= 47: =Qi79 1.1.1.2 root 48: -----END PGP MESSAGE----- 49: md5.c: 50: -----BEGIN PGP MESSAGE----- 1.1.1.3 root 51: Version: 2.6.1 1.1.1.2 root 52: 1.1.1.3 root 53: iQCVAwUBLmkvv8UtR20Nv5BtAQE/jgQAooUL4iKAeg5alJKGvbFqmFlFz0dakkne 54: HnX2dDihBHiapkZ/a2dMCMNbDuxWcUdS5/I4RQfhaLPis9WTeQr2d707c4x5+B4a 55: QPSEAA3fZ0GwX+q8JkZ4XSD3NZbcGJRdudtnp8sYnVY3n7PkzUm6xK7ZcxFxmKTf 56: lTh4Hf3EAaU= 57: =mxp3 1.1.1.2 root 58: -----END PGP MESSAGE----- 59: md5.h: 60: -----BEGIN PGP MESSAGE----- 1.1.1.3 root 61: Version: 2.6.1 1.1.1.2 root 62: 1.1.1.3 root 63: iQCVAwUBLmkvz8UtR20Nv5BtAQHvaAQAq0SZeeArKo5rcRSv25tqa5zFLRDtbZgc 64: dI8JD0st/Dfj8hZf9KWOBiPQbCD5K4U8SWTAJE4qfNkJGM6gf9hXixuZ/DaEzqQr 65: ruXxx0/0/pbx48oVKy08kNL2W3/cguJXQjkK0VbqlYUjgy5zApwbkRgjXw3R1mkF 66: 46A7P51mRLg= 67: =DGCy 1.1 root 68: -----END PGP MESSAGE----- 69: 1.1.1.3 root 70: These signatures were generated by Jeffrey I. Schiller <[email protected]>. 71: Jeff's key is supplied in the keys.asc file in the PGP distribution 72: and is signed by various PGP developers including Phil Zimmermann, so 73: you know that we are who we say we are, and if there are any trojan 74: horses in the source, you know who put them there. Isn't security 75: fun?) 76: -- 1.1 root 77: -Colin <[email protected]> 1.1.1.3 root 78: Revised by Jeffrey I. Schiller <[email protected]>
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.