-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Alogirthm negotitaion fail error after upgrading the JSCH version #596
Comments
Hi @Sai-Srikar, If you would like us to try and help, then you will need to provide a full copy of JSch logs. Thanks, |
hey @norrisjeremy,
We were able to authenticate using password with version 0.1.55, but authentication fails with the upgrade to version 2.0.16. |
Hi @emmymatt, You will need to enable debug logging as that is required for getting the missing log messages from the Thanks, |
Got it @norrisjeremy. Let me get back to you with them. Appreciate the quick response! |
Hey @norrisjeremy just got the logs with DEBUG log level turned on
Unfortunately I could not find any logs from Diff:
|
Hey @norrisjeremy @mwiede following up on this. Debug logs now:
Any insight would be appreciated! thank you! |
Hi @emmymatt, Your server doesn't appear to allow password based authentication, it only allows publickey based authentication. Thanks, |
Hello @norrisjeremy sorry, had to make an update to the logs. |
Hi @emmymatt, If you know that you want to only perform password authentication, then I'd suggest simply instructing JSch to not bother attempting publickey auth. See #608 (comment). Thanks, |
@norrisjeremy Also, could you confirm that when we attempt authentication with password credential and it happens to enter |
Hi @emmymatt, The problem is that you have RSA keys (identities) added to your JSch session that aren't authorized on the server. Thanks, |
Noted @norrisjeremy,
Could you give me more insight on how you concluded this from the debug logs? Apologies in advance if this is a silly question. Shouldn't we have seen this log during these three public key attempts? |
Hi @emmymatt, No, it never attempted password authentication. It attempted publickey only which failed and the server then disconnected you:
Thanks, |
Hey @norrisjeremy could you please look at logs in this message as well? We set |
Hi @emmymatt, The Thanks, |
Thanks for the help @norrisjeremy. Will go through the messages again with my teammates tomorrow to see what I missed here. |
HI
We are in the porcess of upgrading our jsch version from 0.1.55 to 0.2.16
Here we have seen one issue where for the password authentication is working fine on the lower version but failing on the updated version.
On the updated version i am getting following JSCH log
It's never trying the password authentication even though i have set it explicitly like below
session.setConfig("PreferredAuthentications", "password,publickey");
Can you please help me with this
The text was updated successfully, but these errors were encountered: