Stefano Mazzocchi wrote:
Vysper uses TLS via bouncy castle library "bcprov-jdk15-135.jar".
Is there any additional todo deriving from this fact? Is it required
to remove this code from svn until all the steps in crypto.html are done?
I doubt that... also I'm not sure if the board is looking for code that
"uses" crypto or code that "implements" crypto.
The board couldn't care less; except that the federal government does!
There is no difference, however...
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. c
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.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
