From dino.dinoco.de!peti!simons@easix.GUN.de Mon Oct 4 18:09:09 1993 Received: from easix.GUN.de by toadflax.cs.ucdavis.edu (4.1/UCD.CS.2.4) id AA22883; Mon, 4 Oct 93 18:08:30 PDT Received: by easix.GUN.de (Smail3.1.28.1) from dino.dinoco.de with uucp id ; Tue, 5 Oct 93 02:09 GMT Received: by dino.dinoco.de (V1.16/Amiga) id <6zx9@dino.dinoco.de>; Mon, 4 Oct 93 19:37:25 +0200 Received: by peti.GUN.de (V1.16/Amiga) id <0eph@peti.GUN.de>; Mon, 4 Oct 93 13:26:34 CET Date: Mon, 4 Oct 93 13:26:34 CET Message-Id: <9310041226.0epg@peti.GUN.de> In-Reply-To: <9310040018.AA00969@toadflax.cs.ucdavis.edu> (from zerkle@cs.ucdavis.edu (Dan Zerkle)) (at Sun, 3 Oct 93 17:18:32 PDT) X-Mailer: //\\miga Electronic Mail (AmiElm 2.253) Reply-To: simons@peti.GUN.de From: simons@peti.GUN.de (Peter Simons) To: zerkle@cs.ucdavis.edu Subject: Re: MD5SUM Status: RO > You failed to list the complete path name. I think you need something > like /pub/aminet in front of it. I thought I'd better leave this out, because it's different on every system. wuarchive is /pub/systems/..., uni-kl is /pub/amiga/aminet, etc... However, I'll add the path for uni-kl. > You said that you provided the Amiga port and the enhancements. Who > is the original author (or authors)? Yes, your're right. I'll add this. > Also, I'm curious. If someone is going to corrupt an archive, why > would he not corrupt the checksum file to match? This could be > useful, but I don't think in the way you suggest. You do not need to > fix this in your announcement, but you might want to. I have a whole chapter about this problem in the manual and this is indeed not very easy to describe, so I thought I'd better leave it out than to describe it too short. bye, Peter ---8<---------------------------------------------------------------------- TITLE MD5SUM VERSION Version 1 AUTHOR Original version by Branko Lankester and Colin Plumb--Amiga port and enhancements by Peter Simons . DESCRIPTION MD5SUM is a small utility that allows you to build checksums over text- or binary files, using the "MD5 Message Digest Algorithm". These checksums can be stored in a file and can be validated later, using MD5SUM. For example, the checksums of the MD5SUM sources look like this: 107788ec46ef6ab9dbb190215f5b6f1a source/getopt.c ca1ada43f73cff4466adde1e88a8cf60 source/md5.c 4a6dafa2f6282430e65d4728a1303a53 source/md5sum.c So, what is this useful for? Say, you're releasing a software package including sources to the public and want to make shure, nobody modifies the program (for example: add backdoors) and redistributes the modified version. (Do not laugh, this already happened with BBS packages or common utilities. Once, even a virus was added to a utility!) You could include the digest-file with a checksum of every single file in release archive and everybody could easily check the validity of the files. SPECIAL REQUIREMENTS none HOST NAME Any Aminet host, i.e. ftp.uni-kl.de (131.246.9.95). DIRECTORY /pub/amiga/aminet/util/crypt/ FILE NAMES MD5SUM.lha MD5SUM.readme DISTRIBUTABILITY GNU General Public License --------------------------------------------------------------------------- Peter Simons | Usenet: simons@peti.GUN.de | PGP v2.x public key Europaring 20 | CBMNet: simons@peti.adsp.sub.org | available on request 53123 Bonn | Phone: +49 228 746061 | or via GET from almost Germany | CBM: ETG207 | any keyserver. Use it! --------------------------------------------------------------------------- ------------8<-------------------------------------------------------------