Re: [JSch-users] Problem with specific private key

[<ym...@jc...>]

Hi,

   +-From: Alan <ala...@gm...> ---
   |_Date: Wed, 29 Feb 2012 20:07:32 +0000 __
   |
   |What I received was an AES encrypted key (attached as id_rsa, passphrase is
   |'MonoDevelop1') so I initially assumed that we just had to update from our
   |older version of jsch to a newer version. However the encrypted key still
   |did not work with the latest release. I then decided to remove the
   |passphrase and decrypt the key using ssh-keygen. I've attached the
   |decrypted key as 'id_rsa_broken'. JSch was not able to establish a secure
   |connection to github using either the encrypted key or the unencrypted one.
   |There is no problem when we use the commandline git client and that key,
   |nor is there a problem with jsch and the dozens of other keys people have
   |used.

I tried the attached "id_rsa_broken" and "id_rsa",
but I could not reproduce your problem with JSch 0.1.46 and Sun's JDK,
  $ java -version
  java version "1.6.0_29"
  Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
  Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode, sharing)

I have generated its public key by the following command,
  $ ssh-keygen -f id_rsa_broken -y


Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
Skype callto://jcraft/
Twitter: http://twitter.com/ymnk
Facebook: http://facebook.com/aymnk