From owner-freebsd-current  Sat Feb 19 20:10: 4 2000
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7195837BE3B; Sat, 19 Feb 2000 20:09:58 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA42181;
	Sat, 19 Feb 2000 20:09:50 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Kris Kennaway <kris@FreeBSD.ORG>
Cc: Doug Barton <Doug@gorean.org>,
	Victor Salaman <salaman@teknos.com>, freebsd-current@FreeBSD.ORG
Subject: Re: openssl in -current 
In-reply-to: Your message of "Sat, 19 Feb 2000 19:46:50 PST."
             <Pine.BSF.4.21.0002191942240.2430-100000@freefall.freebsd.org> 
Date: Sat, 19 Feb 2000 20:09:50 -0800
Message-ID: <42178.951019790@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Having _a_ general-purpose cryptography toolkit in the base system allows
> us to add in all sorts of cool things to FreeBSD (https support for fetch,
> openssh, random cryptographic enhancements elsewhere). OpenSSL just
> happens to be the only decent freely-available (BSDL) toolkit.

And I still think that this is a reasonable objective, the current
gymnastics for making it happen making me wonder whether or not that
would not be an objective better moved to sometime in September.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message