Date: Mon, 19 Jun 1995 15:50:54 -0400 From: Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: current@FreeBSD.org Subject: Re: Crypto code - an architectural proposal. Message-ID: <9506191950.AA09225@halloran-eldar.lcs.mit.edu> In-Reply-To: <199506191911.MAA01606@gndrsh.aac.dev.com> References: <199506191848.UAA29837@grumble.grondar.za> <199506191911.MAA01606@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 19 Jun 1995 12:11:07 -0700 (PDT), "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> said: > We still can't export the source to libdescrypt.*, but from my understanding > we can export the binary of it. [Is that a correct statement Garrett?] Not quite. libdescrypt was designed in such a way that I believe the State Department would admit that it doesn't actually do encryption, which would then allow you to apply to the Commerce Department for a declaration that it is exportable as ``technical data''. You still have to apply to the State Department first before attempting to export the binary. For extra safefty, the subfunctions called by crypt() could be inlined. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9506191950.AA09225>