I have my own ssh server (on raspberry pi 5, Ubuntu Server 23) but when I try to connect from my PC using key authentication (having password disabled), I get a blank screen. A blinking cursor.
However, once I enter the command eval "$(ssh-agent -s)" and try ssh again, I successfully login after entering my passphrase. I don’t want to issue this command every time. Is that possible?
This does not occur when I have password enabled on the ssh server. Also, ideally, I want to enter my passphrase EVERYTIME I connect to my server, so ideally I don’t want it to be stored in cache or something. I want the passphrase to be a lil’ password so that other people can’t accidentally connect to my server when they use my PC.
Maybe ssh can’t find the key automatically. What is the path to your private key?
I’m pretty sure I generated it to ~/.ssh/id_rsa which I think the default location. It is also the location shown in the terminal image in my post.
As mentioned,
-v(or-vv) helps to analyze the situation.My theory is that you already have something providing ssh agent service, but that process is somehow stuck, and when ssh tries to connect it, it doesn’t respond to the connect, or it accepts the connection but doesn’t actually interact with ssh. Quite possibly ssh doesn’t have a timeout for interacting with ssh-agent.
Using
eval $(ssh-agent -s)starts a new ssh agent and replaces the environment variables in question with the new ones, therefore avoiding the use of the stuck process.If this is the actual problem here, then before running the
eval,echo $SSH_AUTH_SOCKwould show the path of the existing ssh agent socket. If this is the case, then you can uselsof $SSH_AUTH_SOCKto see what that process is. Quite possibly it’s provided bygnome-keyring-daemonif you’re running Gnome. As to why that process would not be working I don’t have ideas.Another way to analyze the problem is
strace -o logfile -f ssh ..and then check out what is at the end of thelogfile. If the theory applies, then it would likely be aconnectcall for the ssh-agent.which sshwhich ssh-agentI guess it’s worth checking if those names point to the expected binaries, but I also think it would be highly unlikely they would be anything else than just
/usr/bin/sshand/usr/bin/ssh-agent.
My theory is that you already have something providing ssh agent service
in the past some xserver environments started an ssh-agent for you just in case of, and for some reason i don’t remember that was annoying and i disabled it to start my agent in my shell environment as i wanted it.
also a possibility is tharlt there are other agents like the gpg-agent that afaik also handles ssh keys.
but i would also look into $HOME/.ssh/config if there was something configured that matches the hostname, ip, or with wildcards* parts of it, that could interfere with key selection as the .ssh/id_rsa key should IMHO always be tried if key auth is possible and no (matching) key is known to the ssh process, that is unless there already is something configured…
not sure if a system-wide /etc/ssh/ssh_config would interfere there too, maybe have a look there too. as this behaviour seems a bit unexpected if not configured specially to do so.
I am not sure I “solved” this but when I add this to my startup script for my terminal (~/.zshrc):
SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket export SSH_AUTH_SOCKit works then. I am not sure I’m still using the ssh agent, but at least it also does not cache my passphrase.
you should definitely know what type of authentication you use (my opinion) !! the agent can hold the key forever, so if you are just not asked again when connecting once more, thats what the agent is for. however its only in ram, so stopping the process or rebooting ends that of course. if you didn’t reboot meanwhile maybe try unload all keys from it (ssh-add -D, ssh-add -L) and see what the next login is like.
btw: i use ControlMaster /ControlPath (with timeouts) to even reduce the number of passwordless logins and speed things up when running scripts or things like ansible, monitoring via ssh etc. then everything goes through the already open channel and no authentication is needed for the second thing any more, it gets really fast then.
I didn’t really follow the former part, but I can give you this:
strace -o logfile -f ssh -p 8322 pi@192.168.2.223 of when I get blank
At the end of the log you find:
822413 connect(4, {sa_family=AF_UNIX, sun_path="/run/user/1000/gcr/ssh"}, 110) = 0 ... 822413 read(4,meaning it’s trying to interact with the ssh-agent, but it (finally) doesn’t give a response.
Use the
lsofcommand to figure out which program is providing the agent service and try to resolve issue that way. If it’s not the OpenSSH ssh-agent, then maybe you can disable its ssh-agent functionality and use real ssh-agent in its place…My wild guess is that the program might be trying to interactively verify the use of the key from you, but it is not succeeding in doing that for some reason.
I am not sure I “solved” this but when I add this to my startup script for my terminal (~/.zshrc):
SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket export SSH_AUTH_SOCKit works then. I am not sure I’m still using the ssh agent, but at least it also does not cache my passphrase/private key
Do you have that file? If not, then
unset SSH_AUTH_SOCKwill work just as well.If it does exist, then I suppose it has good chances of working correctly :).
ssh-add -lwill try to use that socket and list your keys in the service (or list nothing if there are no keys, but it would still work without error).
Can you try
killall sshon the client, and then try to ssh into the rpi again?tried.
what are your ssh config settings: ~/.ssh/config or /etc/ssh/ssh_config
I just added the ~/.ssh/config file on client side:
Host pidoos HostName 192.168.2.223 User pi IdentityFile ~/.ssh/id_rsaSame result.
The /etc/ssh/ssh_config is only relevant on the server side, right? Well, here it is.
sshd_config is server side, ssh_config is client side AFAIK
Your config looks pretty tame. Anything interesting in
/etc/ssh/config.d/?dir does not exist on either side.
yeah I barely changed anything. Just disabled password and changed port AFAIK.
Where is the key? What are the permissions for it?
it got 600 both the private and public key, stored in ~/.ssh/
Often permissions can be an issue. I’d check permission for directory and files and hinr directory for user and group.
Sample permissions here: https://jonasbn.github.io/til/ssh/permissions_on_ssh_folder_and_files.html
Many. Ssh issues I’ve had have been permissions issues.
yeah I copied the permissions as shown, makes no difference. Maybe the ownership is wrong? Both group and owner is me
I am not sure I “solved” this but when I add this to my startup script for my terminal (~/.zshrc):
SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket export SSH_AUTH_SOCKit works then. I am not sure I’m still using the ssh agent, but at least it also does not cache my passphrase (or private key in ram)
I have no idea why but ssh seems to not use keys with different names by default
can you expand on that? What do you mean different names? My PC has of course a different username than the server I’m connecting to. The label name at the end of the key is just a comment, so this is also not what you’re referring to, I think.
By default the key is named id.rsa and ssh-client may only load that. Or none at all. Very strange
Try running ssh with
-vvto get a better idea of the problem when no ssh agent is running.are you using fish shell?
I have zsh
@dysprosium ssh agent manages your ssh keys and automatically passes them as an identity when connecting to a server
If you want to connect without it, you can simply pass
-i \flagokay I tried that, using -i to specify private key. I get the same thing: blank / blinking cursor. When I use verbose -v flag, I see that in BOTH cases (I see about 50 lines) it ends with these two lines:
debug1: Offering public key: /home/username/.ssh/id_rsa RSA SHA256:j3MUkYzhTrjC6PHkIbre3O(etc) agent debug1: Server accepts key: /home/username/.ssh/id_rsa RSA SHA256:j3MUkYzhTrjC6PHkIbre3OT(etc) agentwhere (etc) is some redacted text. It seems the server is ACCEPTING the key, which is nice. But then it’s still a blinking cursor…
@dysprosium Mind trying with -vvvv flag and sharing the output instead of -v?






