Believe it or not but that's exactly what I'm seeing.
I have a program that uses your library. The program has a config file.
The primary function of the program is SFTP client.
In the config file I have a path to the private key file and an IP
address of the SSH server I'm connecting to.
When I'm connecting to the [SSH-2.0-OpenSSH_3.9] server I'm fine and
SFTP works fine too.
When I'm connecting to [SSH-1.99-2.1.0.pl2 SSH Secure Shell] I cannot
get passed user authentication.
Anyhow, I do not want to waste any more of your time. Since the password
authentication works fine for both servers I'll go with the password
authentication for now. I was told that the [SSH-1.99-2.1.0.pl2 SSH
Secure Shell] server will be upgraded soon.
On a different topic(s):
Is there a way I can help you in your development effort? I checked
http://www.jcraft.com/jsch/ there is nothing specific there. I saw that
you accept changes over e-mail. Is it the only way to contribute?
After using your library for some time now I realized that it would
benefit from adding a logging functionality. What I did was I replaced
your System.err.println with calls to info() from java.util.logging.*
That helped me a lot since I'm running my programs (and your library) in
a batch mode without user interface.
UserAuthPassword class caused me some grief as it was going into an
infinite loop when the publikey authentication failed and the password
I added "count--; if (count =3D=3D 0) return false;" to solve the
problem. Maybe I could have done a better design of my UserInfo
interface implementation, since my userinfo.promptPassword() always
returns true and there is no user to cancel that when I run in a batch
And the last but not least, I'd love to see unit tests for your library.
Something like JUnit would do. Do you have any plans for that?
From: Atsuhiko Yamanaka [mailto:ymnk@...
Sent: Tuesday, September 19, 2006 10:43 AM
To: Edward Pelyavskyy
Subject: Re: [JSch-users] Getting SSH_MSG_USERAUTH_FAILURE with DSA key
Thank you for prompt reply.
I have another question.
>The same DSA key works fine with [SSH-2.0-OpenSSH_3.9] server.
>Can it be that [SSH-1.99-2.1.0.pl2 SSH Secure Shell] is the problem?
Do you mean that you can login to SSH-2.0-OpenSSH_3.9 server with
'/tmp/keys/mykey', but you can not login to 'SSH-1.99-2.1.0.pl2=20
SSH Secure Shell' server with the same private key, '/tmp/keys/mykey'?
Frankly to say, I can not find the reason. If you can login to
OpenSSH server, requests about public-key auth must be valid and
those requests should be also valid for such a proprietary sshd from
the ssh2 protocol point of view.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
This transmission (including any attachments) may contain confidential =
information, privileged material (including material protected by the =
solicitor-client or other applicable privileges), or constitute =
non-public information. Any use of this information by anyone other than =
the intended recipient is prohibited. If you have received this =
transmission in error, please immediately reply to the sender and delete =
this information from your system. Use, dissemination, distribution, or =
reproduction of this transmission by unintended recipients is not =
authorized and may be unlawful.