From owner-freebsd-ports Tue Jul 11 22:45:37 2000 Delivered-To: freebsd-ports@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 901FB37BB64; Tue, 11 Jul 2000 22:45:34 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca14-12.ix.netcom.com [205.186.215.12]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id BAA00539; Wed, 12 Jul 2000 01:44:53 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id WAA65749; Tue, 11 Jul 2000 22:43:00 -0700 (PDT) To: "Jordan K. Hubbard" Cc: freebsd-ports@freebsd.org, kris@freebsd.org, archie@freebsd.org Subject: Re: Export controlled ports References: <22185.963379859@localhost> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 11 Jul 2000 22:41:57 -0700 In-Reply-To: "Jordan K. Hubbard"'s message of "Tue, 11 Jul 2000 22:30:59 -0700" Message-ID: Lines: 17 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: "Jordan K. Hubbard" * You know, it might be cool if we could still preserve, somehow, the * fact that this is in the crypto category. Not make it a restriction, * just preserve it as a classification in case anybody inside Vietnam or * China or someplace with their _own_ problematic and self-defeating set * of laws on cryptography import or export needs to know which ports are * which. What do you think? Well, they are all marked with "### crypto", I can make that a rule instead of just an example. Beyond that, I'm not really excited about adding Yet Another Knob (YAK) to a collection that already has too many special cases that I'm working hard to eliminate. -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message