-
Notifications
You must be signed in to change notification settings - Fork 603
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
Authentication problem using ECDSA 521 private key #521
Comments
Can you send the debug logging of the full connection/login attempt? |
Sure, I anonymized fingerprint, ip address and some class names.
|
If necessary, I can provide code itself as a separate project |
Can you add a slf4j logger implementation and ensure that there is debug
level logging? Currently no logger is configured (noop).
Op wo 17 jul. 2019 15:11 schreef alperenp <notifications@github.com>:
… If necessary, I can provide code itself as a separate project
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#521?email_source=notifications&email_token=AAA4XI3WTTOLJCBJBSBFJWDP74K7VA5CNFSM4IEOHDWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2EEOCQ#issuecomment-512247562>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA4XI3TPKT6ADPLWW4AL4LP74K7VANCNFSM4IEOHDWA>
.
|
Here is code
Here is log
|
If needed, I created my key pair with following command: And my private key is in he form of
|
Hello again, I just find that I can authenticate as expected using 256 bit ECDSA key with the same code piece. So maybe there is something wrong ongoing with 521 bit (Which I believe the array copy part on is the root cause at net.schmizz.sshj.signature.SignatureECDSA.encode(SignatureECDSA.java:96)). I put the working log as well maybe you can distinguish something
|
Hello again, |
This issue appears to be resolved in PR #623. |
Hey there, I've been using sshj for some time, thanks for such nice tool and continue on your improvements!
I encounter a problem when I try to use ecdsa-sha2-nistp521 key. This could be duplicate issue but I couldn't find it from previous issues and in other public sources.
Here is the deal, I have a private ECDSA key and a remote server which I can connect successfully over ssh. While using sshj, I receive
Here is how I try to do the magic
Possibly related:
On my first trial of SSHClient creation, I receive the following (when calling connect(ip, port, poxy) method) and then I try to create with the fingerpint.
I've tried adding BouncyCastle as
Security.addProvider(new BouncyCastleProvider());
however, it didn't change the result. If you can give a hand, it would be appreciated!Specifications:
The text was updated successfully, but these errors were encountered: