remaining question: if I want vault to hold several SSH keys, should I best
(a) replace the single ssh-add command by "ssh-add c /path/to/key1 &&
ssh-add -c /path/to/key2"
or
(b) create a ssh-add-my-keys.sh containing
ssh-add -c /path/to/key1
ssh-add -c /path/to/key2
ssh-add -c /path/to/ke
Solved. Stupid me!
> I re-checked, my /etc/qubes-rpc/policy/qubes.SSHagent says only
one line, namely
ssh-client vault ask
which I find odd (= I do not understand), since in the nomenclature of
the man-page, ssh-client=work not vault, right?
it is of course either
"@anyvm vault ask" or "wor
Thank you.
>> We observe that the file /run/user/1000/openssh_agent is different
>> from /home/user/.SSH_AGENT_sshkeys. That may be a problem.
You seem to be running the "ssh-agent.service" in your work qube. This
is not part of the linked setup guide. There only one agent is running
and t
On 21/06/2023 11:49, haaber wrote:
>> We observe that the file /run/user/1000/openssh_agent is different
>> from/home/user/.SSH_AGENT_sshkeys. That may be a problem.
Running the following command in the work qube should work:
SSH_AUTH_SOCK=/home/user/.SSH_AGENT_vault ssh-add -L
You
update: somewhere I wrote "vault", somewhere "sshkeys". Correcting this
does NOT resolve the problem :((
On 6/21/23 11:45, haaber wrote:
I tried to follow carefully the split-ssh instructions on
https://github.com/Qubes-Community/Contents/blob/master/docs/configuration/split-ssh.md
but I expe
