-
Notifications
You must be signed in to change notification settings - Fork 160
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
unable to monitor server, error message not helpful. #13
Comments
Hmm, maybe it is picking up the key file auth method first, before the ssh-agent method. Can you try an experiment please?
|
for the record, and I don't know if this is explicitly the cause, but I use keychain rather than ssh-agent. It still registers the environment variables though. :\ |
I think addAgentAuth is failing, because it should be getting the key from the agent. |
Hmm, it does for me. Can you try with a non-password-protected private key? |
Sorry for the slow reply. Now I'm REALLY confused.
wut. the key works on its own, but fails on its own for rtop. How is that... what?! |
I can confirm that removing a passphrase from private key resolves this: obviously, not something you want to do in general |
Yah I likely am hitting another issue entirely, it might not be related to the private key password. |
Please check with commit f753d19. With this rtop will natively support encrypted private keys, and also support auth via ssh-agent correctly. |
Ah it's asking me for a key now, I think this is likely working, but I may be suffering from a different issue as well, seeing as the unecrypted pup key doesn't work. I can't confirm this is a solved issue, should I open another one? |
Try with the latest commit ba5b35e. This improves the auth method handling. |
sooo there are some problems here. Even with the correct password that I just set on that machine, it fails to authenticate. It's not pulling the pubkey from the ssh agent (keychain). this is frustrating, I don't understand what's going wrong here. |
Hmm, ssh appears to be using the agent, since it is not asking for the passphrase of the encrypted private key at ~/.ssh/id_rsa. (Or its reusing a connection via ControlMaster). Assuming the rtop was properly compiled off ba5b35e, this probably means that rtop is not able to talk to the agent. Rtop uses the env var SSH_AUTH_SOCK to get the Unix socket name to talk to. This is usually set by running "eval $(ssh-agent)" in the shell. Can you check this flow? |
those environment variables are set.
so this is very strange! |
Is the env var being exported? Can you run "bash" again and in it "env" again? |
:( also there really is something screwy going on here. I am connecting to a server that knows my public key, it also has a password and I provided that. I just can't connect to that server. Providing repeated correct credentials. |
Hmm. Try connecting to another server? Try running rtop from another machine? |
so that's strange. I tried manually providing the private key to use, but the same result happened.
Keeping in mind that my private key is password protected, and the ssh-agent currently has access to it unencrypted.
Not sure what's going on :<
The text was updated successfully, but these errors were encountered: