Re: [JSch-users] Export control issues for JSch

[Oberhuber, M. <Mar...@wi...>]

Hello Gian Luca,
=20
it might help you to know that jsch-0.1.28 is part of Eclipse 3.2, and
Eclipse says:
=20
Cryptographic content from the Eclipse Foundation has been given a
classification as Export Commodity Control Number (ECCN) 5D002.C.1 by
the U.S. Government Department of Commerce, Bureau of Export
Administration, and is deemed eligible for export under License
Exception ENC Technology Software Unrestricted (TSU) for object code and
(cryptographic) source code.
=20
See http://www.eclipse.org/legal/committerguidelines.php # Cryptography
=20
Anyways it would be interesting to hear other statements too...

Cheers,
Martin
--
Martin Oberhuber - WindRiver, Austria
+43(662)457915-85


=20


________________________________

	From: jsc...@li...
[mailto:jsc...@li...] On Behalf Of ORTELLI
Gian Luca
	Sent: Wednesday, July 05, 2006 10:28 AM
	To: jsc...@li...
	Subject: [JSch-users] Export control issues for JSch
=09
=09

	=20

	Hi,

	=20

	We are embedding JSch (version 0.1.26) in a product which we
sell in many countries of the world, and therefore we need to know about
export control-related problems.=20

	I know that JSch does not implement encryption directly, but it
uses default cryptographic providers of JVM (from JVM 1.4.x). And a
check on the code reveals that "critical" classes, like AES128CSC.java,
are empty, in the sense that they simply request the cipher
implementation from JVM.=20

	Is that really so? We need to be sure before starting the job.

	=20

	Thanks,

	=20

	=20

	Gianluca Ortelli

	=20

	=20

	=20

	=20

=09
	=20

	=20