From owner-freebsd-hackers Tue Oct 28 11:55:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15920 for hackers-outgoing; Tue, 28 Oct 1997 11:55:42 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15915 for ; Tue, 28 Oct 1997 11:55:31 -0800 (PST) (envelope-from brandon@roguetrader.com) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id MAA20082 for ; Tue, 28 Oct 1997 12:55:31 -0700 (MST) Date: Tue, 28 Oct 1997 12:55:30 -0700 (MST) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: more general checksum command, replacing md5? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just curious, with the inclusion of SHS hashing in crypt(), would anybody consider a generalized checksum command? It wouldn't be too hard to make a general 'cs' or 'checksum' command that accepts arguments to determine the algorithm being used... ala: cs -md5 cs -shs Etc... With multiple algorithms, I'd also suggest having the checksum command be capable of doing the comparison, so it could know what to do based off the existing checksum it is being compared to, ala: cs -check 'MD5 (foof) = 092eb830a343bf1fad2e522834cf346e' < foof cs -checkf foof.md5 < foof Would exit ''true'' or ''false'' depending upon if the check was good. Just curious, I suppose the other alternative would be to make an 'shs' command similar to 'md5'.. but that seems unclean.. -Brandon