From owner-cvs-all Sun Dec 5 21:24:46 1999 Delivered-To: cvs-all@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 90E1E1506A; Sun, 5 Dec 1999 21:24:41 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id AAA07158; Mon, 6 Dec 1999 00:24:20 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Mon, 6 Dec 1999 00:24:20 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Nate Williams Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/security/openssh Makefile In-Reply-To: <199912060512.WAA23774@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk I'm already open to all the same risks, since the "patches" contain parts of the OpenSSH code. Either none of the port is RESTRICTED, or the port _itself_ is RESTRICTED. Preventing the export of the package (containing the code in machine-usable format), since some of the code is exported in other ways (files/, patches/, etc), is nonsensical. RESTRICTED serves no purpose of legality, only to make things less convenient. I am speaking only of the OpenSSH port here, but it applies to others... -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message