William A. Rowe, Jr. wrote:
Stefano Mazzocchi wrote:
Those seem to be two different things as far as export regulation goes
(in fact, you could ship Vysper without crypto and the users can
obtain it themselves if they want it/need it.
IF Vysper doesn't ship crypto - e.g. BouncyCastle, AND does not call any
cryptographic functions of BouncyCastle, then it is not the labs' issue.
E.g. [...]
if you use BouncyCastle to create a cryptographically secure hash identifier
or password token, it's not "crypto". If use BouncyCastle to encrypt a data
stream, that is crypto.
But if you make a call to enable a secure channel, etc, then yes a notice
must be sent and it should be tracked on the /licenses/exports page.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
