From owner-freebsd-current Wed May 17 0:50: 8 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 AB25D37BA66; Wed, 17 May 2000 00:50:03 -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 AAA11793; Wed, 17 May 2000 00:52:40 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: OpenSSH 2.1 In-reply-to: Your message of "Tue, 16 May 2000 12:16:57 PDT." Date: Wed, 17 May 2000 00:52:40 -0700 Message-ID: <11790.958549960@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But I'm suddenly confused what you're actually talking about > here: OpenSSH, OpenSSL, or RSAREF. > > OpenSSH has never included crypto code, but it's useless without OpenSSL > which quite certainly does. OpenSSH no longer requires RSAREF to operate > (if you've got clients/servers willing to do DSA SSH2), which is the > "non-free" component I was talking about. OK, if OpenSSL still contains crypto then "never mind"; I thought OpenSSL used *only* RSA and it used it through the RSAstubs code, making it "OK." > today as well (after you've checked and got that legal advice I've been > bugging you about :) I'm working on the legal advice; a firm has been retained and consulted. Some paperwork needs to be done in order to get FreeBSD an export permit and I'm still working on figuring out if this will be an ongoing issue or we can just do it once. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message