From owner-freebsd-audit Wed May 2 18:33:11 2001 Delivered-To: freebsd-audit@freebsd.org Received: from casimir.physics.purdue.edu (casimir.physics.purdue.edu [128.210.146.111]) by hub.freebsd.org (Postfix) with ESMTP id C5E6737B424; Wed, 2 May 2001 18:33:08 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: by casimir.physics.purdue.edu (Postfix, from userid 1000) id 2784B1C0E3; Wed, 2 May 2001 20:28:51 -0500 (EST) Date: Wed, 2 May 2001 20:28:51 -0500 From: Will Andrews To: Dima Dorfman Cc: Poul-Henning Kamp , audit@FreeBSD.org Subject: Re: sha1 support in md5(1) Message-ID: <20010502202850.G5017@casimir.physics.purdue.edu> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Dima Dorfman , Poul-Henning Kamp , audit@FreeBSD.org References: <20010502200930.F5017@casimir.physics.purdue.edu> <20010503012023.A8BA03E2B@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Obg6o3IqMqKlkF6F" Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010503012023.A8BA03E2B@bazooka.unixfreak.org>; from dima@unixfreak.org on Wed, May 02, 2001 at 06:20:23PM -0700 X-Operating-System: Linux 2.2.18 sparc64 Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Obg6o3IqMqKlkF6F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 02, 2001 at 06:20:23PM -0700, Dima Dorfman wrote: > If we can get the OpenSSL folks to stick those spaces in there for us > that'd be the best. Then, we just add links for 'md5', 'sha1', > etc. to openssl in /usr/bin (I've always thought /sbin was a bad place > for md5(1), anyway). Failing that, we find a way to run the output > through something like: >=20 > sed -E 's/^(.+)\((.+)\)=3D (.+)$/\1 (\2) =3D \3/g' >=20 > and make links to that. I agree that /sbin seems like a bad place for a tool like md5(1). Does anyone have any idea why it is? I'm kinda iffy on the idea of making a hack like you suggest. IMO, perhaps for the sake of standardization we should simply drop md5(1) and provide links for OpenSSL. I think that the scripts that would break would only gain from the standardization by not needing any "special" code for FreeBSD anymore (of course this is mainly for people who do crossplatform scripts, though I guess OpenSSL is a bit of a new thing). Ports can easily make the transition since all supported versions of FreeBSD already have OpenSSL. Perhaps Poul-Henning would like to comment on this. --=20 wca --Obg6o3IqMqKlkF6F Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE68LRSF47idPgWcsURAoxxAJ4/jvW9wC5SgSJIrydQqx0nU9JfFQCfQbYB N7tBCehaYX9Ljx4RpNz7R34= =OMVH -----END PGP SIGNATURE----- --Obg6o3IqMqKlkF6F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message