Skip to content
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

Suitable identity not found #147

Open
equinayzz opened this issue Jul 16, 2024 · 1 comment
Open

Suitable identity not found #147

equinayzz opened this issue Jul 16, 2024 · 1 comment

Comments

@equinayzz
Copy link

So I am new to ssh3. I want to try the hiding server features. I've done all the installation steps. Then I start the ssh3 server using command sudo ssh3-server -bind 17.0.2.12:8081 -url-path /top and when I try connecting via the client using ssh3 [email protected]:8081/top I get this result:
11:56AM ERR could not dial 17.0.2.12:8081/top: no suitable identity found
Can you tell me what the possible cause of this is?

@jeroen-80
Copy link

jeroen-80 commented Nov 5, 2024

Exactly the same here:

  • Using gpg-agent to communicate with token with SSH private key.
  • ~/.ssh/authorized_keys present on the server.
  • Agent based logon working on SSH2 (e.g. PuTTY), SSH_AUTH_SOCK is set on the client.
  • Password based logon with SSH3 works, so the setup seems ok.
  • Key based logon -privkey ~/.ssh/id_rsa with SSH3 works.
  • Agent based logon NOT working on SSH3: ERR could not dial <redacted>:443/topsecret: no suitable identity found.
  • Both key and agent used ssh-rsa keys.

It might be good to add agent related info to the verbose mode, nothing seen in both server and client logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants