this post was submitted on 14 Aug 2024
118 points (98.4% liked)

Linux

48364 readers
1587 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] Uberflussig@sh.itjust.works 1 points 3 months ago (1 children)

What happens if you do:

unset  SSH_AUTH_SOCK

And then try to connect?

[–] dysprosium@lemmy.dbzer0.com 2 points 3 months ago (1 children)

Hey that works too! Same effect as my previous workaround, that I just posted yesterday.

I do have to repeat this command everytime, so I had to put it into ~/.zshrc so it's executed beforehand in every new terminal.

It still does feel lile a workaround since it 'resets' itself (as I said) with every new terminal.

[–] Uberflussig@sh.itjust.works 1 points 3 months ago

So, this is set somewhere in your config files, I think. Maybe try:

grep -r SSH_AUTH_SOCK /etc
grep -r SSH_AUTH_SOCK ~/.*

Just to see where it's being set.