From owner-freebsd-ports Tue Jul 11 12:53:31 2000 Delivered-To: freebsd-ports@freebsd.org Received: from zippy.osd.bsdi.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9316A37BB05; Tue, 11 Jul 2000 12:53:28 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA11334; Tue, 11 Jul 2000 12:53:49 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Cc: "Chris D. Faulhaber" , freebsd-ports@freebsd.org, jkh@freebsd.org Subject: Re: Export controlled ports In-reply-to: Your message of "11 Jul 2000 12:19:05 PDT." Date: Tue, 11 Jul 2000 12:53:49 -0700 Message-ID: <11331.963345229@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From my reading of this, it covers all the software we ship with FreeBSD, something which includes packages and, by inference, the ports collection. - Jordan > * From: "Chris D. Faulhaber" > > * Now that FreeBSD's source tree has been unified WRT crypto sources, what, > * if any, are the implications for crypt/export-controlled ports now? > > That's a good question. Jordan? Does the permission BSDi got extend > to ports too, or is it only for src? > > Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message