-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Issue with DSA public key #8
Comments
Is this the correct usage for a DSA key:
Proc-Type: 4,ENCRYPTED O78kfuI+szElw9lCRHB9xC3G8wztPpGIjZie9Ogt4Xs7Tp0uZI2kixdi6s3xa5Kd |
That is the right usage for a DSA key, at least as 'passphrasse' is the password/phrase for you DSA key. |
Yes. It works with Putty and FileZilla, so connection with the key is possible. |
I added some extra logging: signature OK But if I remove method password, I get this: signature OK I have the impression that some of the response messages are responses from older messages being sent to the server... |
This very helpful. I will look into it. I couldn't reproduce it myself |
Hi, I can try to make 2 attempts of method none, and see if the method password works on 3rd attempt on my server. |
I've attached another version, which first tries the private key method, then the password method and if still not yet logged in the none method. |
I added this around the password try:
... In other words, the 'password' method is skipped if the server indicates it is not supported. That solves my problem too |
Nice to hear your problem is solved. Curious to know what SFTP-server you use by the way, as that behaviour is not according RFC-4252. |
Hi all,
While trying to connect with a server using key authentication, I always get this error:
try ssh-dss public key
ssh-dss public key not OK
ORA-20030: Could not login.
I tested the key with putty and FileZilla from different client PCs, without problems, but with the package it does not seem to work.
I cannot test another type (e.g. RSA) as DSA is the only type supported at the moment.
The text was updated successfully, but these errors were encountered: