From owner-freebsd-security Thu Dec 16 12:47:51 1999 Delivered-To: freebsd-security@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id E758715774; Thu, 16 Dec 1999 12:47:43 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id VAA19515; Thu, 16 Dec 1999 21:47:36 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA80111; Thu, 16 Dec 1999 21:47:36 +0100 (MET) Date: Thu, 16 Dec 1999 21:47:35 +0100 From: Eivind Eklund To: Peter Wemm Cc: Brian Fundakowski Feldman , Mark Murray , Kris Kennaway , security@FreeBSD.ORG Subject: Re: OpenSSH in the base (was Re: OpenSSL update) Message-ID: <19991216214735.J62815@bitbox.follo.net> References: <19991216202404.92CBA1CC6@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991216202404.92CBA1CC6@overcee.netplex.com.au>; from peter@netplex.com.au on Fri, Dec 17, 1999 at 04:24:04AM +0800 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 17, 1999 at 04:24:04AM +0800, Peter Wemm wrote: > It's not a crypto export problem, it's the RSA patent that's the problem. > Any code that isn't RSAREF based for RSA support is unusable in the US. I > don't think OpenSSL linked against RSAREF is useable for OpenSSH. You think wrong. (OpenSSL linked against RSAREF is what OpenBSD use to be able to export OpenSSH to the US, which I assume mean it is usable.) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message