Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!cronkite.cisco.com!pst From: pst@cisco.com (Paul Traina) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD outside of US?? Date: 23 Aug 1993 18:48:12 GMT Organization: cisco Systems, Menlo Park, California, USA Lines: 17 Message-ID: <PST.93Aug23114812@cider.cisco.com> References: <WS.93Aug22212223@kurt.tools.de> <258qov$i3e@landin.ecs.soton.ac.uk> <1993Aug23.083546.5676@gmd.de> <25aru3$cdv@umd5.umd.edu> NNTP-Posting-Host: cider.cisco.com To: mark@roissy.umd.edu (Mark Sienkiewicz) In-reply-to: mark@roissy.umd.edu's message of 23 Aug 1993 08:40:35 PST In article <25aru3$cdv@umd5.umd.edu> mark@roissy.umd.edu (Mark Sienkiewicz) writes: I propose that the solution is this: 1. *BSD should have a common source and object tree without encryption. 386bsd 0.1 did this. 2. There should be a US encryption package. This should be distributed only within the US. 3. There should be a non-US encryption package. This should be distributed only outside the US. There is no need for 2, people in the US can use a foreign encryption package, you just can't re-export it _from the US_. -- nequaquam vacuum