From owner-freebsd-security  Mon Jul 24 11:56:31 1995
Return-Path: security-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id LAA05241
          for security-outgoing; Mon, 24 Jul 1995 11:56:31 -0700
Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA05235
          for <security@freebsd.org>; Mon, 24 Jul 1995 11:56:29 -0700
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA25903; Mon, 24 Jul 1995 12:57:35 -0600
Date: Mon, 24 Jul 1995 12:57:35 -0600
Message-Id: <199507241857.MAA25903@rocky.sri.MT.net>
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Cc: mark@grondar.za (Mark Murray), pst@stupi.se, security@freebsd.org,
        freebsd-foreign-secure@grondar.za
Subject: Re: secure/ changes...
In-Reply-To: <199507241723.KAA19257@gndrsh.aac.dev.com>
References: <199507241641.SAA23989@grumble.grondar.za>
	<199507241723.KAA19257@gndrsh.aac.dev.com>
Reply-To: nate@sneezy.sri.com (Nate Williams)
From: nate@sneezy.sri.com (Nate Williams)
Sender: security-owner@freebsd.org
Precedence: bulk

> 
> As already pointed out no less than 2 times, DES is a munition, importing
> munitions is just as regulated as exporting them.  Makeing freefall's cvs/
> secure bits a slave to the ZA site is just as much a problem as exporting
> the bits from freefall :-(.

Actually, I almost positive that you can import the sources w/out any
problems, it the export that will give you grief.  Sean Fagan seemed to
know the skinny on this.


Nate