Great comments. The key is "off the shelf". If it is a retail product, then approval seems easy (although every specific build that changes crypto functions or the way that crypto functions are called is subject to a new approval process). Otherwise, evidently it is much more dicy.
... just a developer trying to get along ... David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rich Salz Sent: Thursday, May 30, 2002 1:38 PM To: David Smith Cc: [EMAIL PROTECTED] Subject: Re: US Export (was RE: your mail) This is verging off-topic for this list, but ... My experiences are much simler than David's (perhaps because I've been doing this since I first inadvertantly posted DES to Usenet in 1986?:) At my previous company we built an "off the shelf" product that did signatures and encryption. Our product manager found the form, filled it in (our crypto all came from openssl), and we got export approval in a couple of weeks. /r$ ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
