From owner-freebsd-current  Mon May 15 23:12:54 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 5D13037B5BE; Mon, 15 May 2000 23:12:49 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from localhost (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA54372;
	Mon, 15 May 2000 23:14:46 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: Kris Kennaway <kris@FreeBSD.org>
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.org
Subject: Re: OpenSSH 2.1 
In-reply-to: Your message of "Mon, 15 May 2000 21:54:52 PDT."
             <Pine.BSF.4.21.0005152154080.47631-100000@freefall.freebsd.org> 
Date: Mon, 15 May 2000 23:14:46 -0700
Message-ID: <54363.958457686@localhost>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Err, well it still requires openssl, which I think is firmly rooted in the
> crypto distribution as long as we have one.

Is it?  I thought the RSAref code being pluggable gave it some
protection, or is merely "pluggability" also classified as crypto? 
I do recall someone saying something to that effect once...

- Jordan


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