From owner-freebsd-hackers Tue Oct 28 17:57:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA09903 for hackers-outgoing; Tue, 28 Oct 1997 17:57:47 -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 RAA09898 for ; Tue, 28 Oct 1997 17:57:44 -0800 (PST) (envelope-from brandon@roguetrader.com) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id SAA22651; Tue, 28 Oct 1997 18:57:30 -0700 (MST) Date: Tue, 28 Oct 1997 18:57:29 -0700 (MST) From: Brandon Gillespie To: Mikael Karpberg cc: freebsd-hackers@FreeBSD.ORG Subject: Re: more general checksum command, replacing md5? In-Reply-To: <199710290116.CAA07555@ocean.campus.luth.se> 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 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' > Having more then one general checksum program seems to be overdoing it. my point exactly.