From owner-freebsd-hackers Tue Oct 28 18:41:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA12356 for hackers-outgoing; Tue, 28 Oct 1997 18:41:28 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA12345 for ; Tue, 28 Oct 1997 18:41:05 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id DAA07742; Wed, 29 Oct 1997 03:48:41 +0100 (CET) From: Mikael Karpberg Message-Id: <199710290248.DAA07742@ocean.campus.luth.se> Subject: Re: more general checksum command, replacing md5? In-Reply-To: from Brandon Gillespie at "Oct 28, 97 06:57:29 pm" To: brandon@roguetrader.com (Brandon Gillespie) Date: Wed, 29 Oct 1997 03:48:41 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Brandon Gillespie: > On Wed, 29 Oct 1997, Mikael Karpberg wrote: > > > According to Brandon Gillespie: > > > 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: > > > > Er... Why not, in that case, just add those options to the chsum program? > > Because the checksum program is 'md5' I meant the 'cksum' program, ofcourse. And as you say, the one used is the md5 program. That should have been an option in 'cksum' too, instead, I think. Ofcourse, it could detect name started with to auto-select algorithm. That way md5 could be made a hardlink to cksum. /Mikael