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

[ORTELLI G. L. <Gia...@si...>]

Thank you,

this is the answer I was looking for: there is no encryption code in the
library.=20
I guess this means that we don't have to worry about export restrictions
(except for those on JRE).=20

Yours,

Gianluca Ortelli


-----Original Message-----
From: Atsuhiko Yamanaka [mailto:ym...@jc...]=20
Sent: Wednesday, July 05, 2006 11:16 AM
To: ORTELLI Gian Luca
Cc: jsc...@li...
Subject: Re: [JSch-users] Export control issues for JSch

Hi,

   +-From: "ORTELLI Gian Luca" <Gia...@si...> --
   |_Date: Wed, 5 Jul 2006 10:27:41 +0200 ______________________
   |
   |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.
   |Is that really so? We need to be sure before starting the job.

I can not understand what you mean 'empty', but it is right that
jsch will use AES encryption through the AES implementation provided=20
by JCE(Java Cryptography Extension) provider included in J2SE 1.5(and
later).
So, jsch does not implement any encryption functions by itself and
jsch does not include any java byte code for encryption in its jar file.


Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
    +1-415-578-3454
Fax +81-22-224-8773
Skype callto://jcraft/