Date: Mon, 18 Dec 2000 03:19:52 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: Kurt@pinboard.com, Kris Kennaway <kris@FreeBSD.ORG>, freebsd-security@FreeBSD.ORG Subject: Re: mcrypt Message-ID: <20001218031952.A27637@citusc.usc.edu> In-Reply-To: <20001217221044.B57851@pinboard.com>; from Kurt@pinboard.com on Sun, Dec 17, 2000 at 10:10:44PM %2B0100 References: <20001216234910.A14562@pinboard.com> <20001217013331.B18038@citusc.usc.edu> <20001217221044.B57851@pinboard.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 17, 2000 at 10:10:44PM +0100, Kurt@pinboard.com wrote: > On Sun, Dec 17, 2000 at 01:33:31AM -0800, Kris Kennaway wrote: > > Just use the port. cd /usr/ports/security/mcrypt && make install clean. >=20 > libmcrypt, libmcrypt-nm and mhash are available as ports, but I > could not find mcrypt. mcrypt is a program using libmcrypt and mhash. Hmm, you're right. Well, just use openssl then since it's easier to install. > > It might also be easier to just use openssl, which is in all post 4.0 >=20 > The machines in question range from 3.1 to 4.1. And it's not just about > the *transport* of files, but also about the *storage* on remote machines. Yes, openssl can do that too. Kris --yrj/dFKFPuw6o+aM 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 iD8DBQE6PfLYWry0BWjoQKURAuPsAKC0+6/odf6Sd20GNST10SKmiCkv4gCeKrPR oNifv4BvWljnOAjzWc4a2ZA= =VKbr -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001218031952.A27637>