Communities

Writing

Codidact Meta

The Great Outdoors

Photography & Video

Scientific Speculation

Cooking

Electrical Engineering

Judaism

Languages & Linguistics

$Mathematics$

tag:snake search within a tag

answers:0 unanswered questions

user:xxxx search by author id

score:0.5 posts with 0.5+ score

"snake oil" exact phrase

votes:4 posts with 4+ votes

created:<1w created < 1 week ago

post_type:xxxx type of post

Search help

Notifications

Mark all as read See all your notifications »

Q&A Meta

Q&A

Posts Tags Edits

Ask Question

Comments on How to let systemd user unit see keys in SSH agent?

Post

How to let systemd user unit see keys in SSH agent?

+0

−0

I have a script that does git fetch for a repository. When I run this in my shell it works fine.

I want to run it in a systemd user unit. However, I am using an SSH url, and the systemd unit fails with fatal: Could not read from remote repository.' (Git exit code 128).

This is probably because systemd doesn't have access to my SSH key and/or cannot handle the interactive passphrase prompt.

I've seen solutions like creating a passwordless SSH key, but I don't want to do that. I also don't want to explicitly point it to the key, because this will be on several machines that have differently named keys. I'd rather make the systemd unit get the SSH key the same way git fetch does for me: From the SSH agent. How can I do that?

posted over 1 year ago

CC BY-SA 4.0

matthewsnyder‭

1806 reputation 122 75 285 109

Raw

Markdown

History

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

1 comment thread

Probably not a supported use case (2 comments)

bgstack15‭ wrote over 1 year ago

copy link

You should check to see if you can set the permissions (including SELinux?) for the running ssh-agent socket, and also set the environment variables somehow, so that this process can talk to the existing ssh-agent. When something runs ssh-agent, ssh-agent normally prints its sock and pid:

$ ssh-agent 
SSH_AUTH_SOCK=/tmp/ssh-rIEUSojPzs0W/agent.9298; export SSH_AUTH_SOCK;
SSH_AGENT_PID=9299; export SSH_AGENT_PID;
echo Agent pid 9299;

You need to share this info somehow for your systemd unit to pick up, maybe with predictable socket filenames or perhaps if just running ssh-agent again generates the same pid+socket file output?