From owner-freebsd-security Mon Oct 11 23:10:15 1999 Delivered-To: freebsd-security@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3913A15180 for ; Mon, 11 Oct 1999 23:10:14 -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 XAA02592; Mon, 11 Oct 1999 23:10:42 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: tom brown Cc: security@FreeBSD.ORG Subject: Re: Is it just me or is the ssh port broken for Release 3.3? In-reply-to: Your message of "Mon, 11 Oct 1999 20:55:16 PDT." <19991012035516.7083.rocketmail@web109.yahoomail.com> Date: Mon, 11 Oct 1999 23:10:42 -0700 Message-ID: <2588.939708642@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > So as I have done many times before I go to the ports > collection and try to make ssh. > > As always it takes an eternity to download from > finland. It always works for me, so it's probably premature to start suspecting the involvement of black helicopters and such here. > 1. Why is such an importaint package as rasref20 > broken?(Is it to allow the NSA to trojan it?) It's not broken. > 2. Now the US govenment have dropped the export > control law's, can we have these components ether on > the CD-ROM or the the main website? 1. The US government has done no such thing. Go read the press on this again and you'll find that you still need to *apply* for export privileges, something we've done but will only affect FreeBSD in any case and not rsaref. 2. rsaref isn't restricted due to export controls, it's restricted due to PATENT issues with RSA. Until RSA's patent expires, Clinton's administration can relax export controls all they want and it won't affect rsaref one bit. People need to do a bit more homework in informing themselves before reaching for conspiracy theories. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message