There are ways to find the PID and socket of a running ssh-agent but they seemed pretty janky. How can I either disable the autostarted ssh agent and use one I start myself via systemd, or get the environment variable to the autostarted KeePassXC instance? Just starting an ssh-agent with systemd according to this arch wiki article as mentioned in the last comment on this issue does not work because of the aforementioned behaviour. I use Ansible already with keepassxc on my Desktop which works fine but Im going to set up another vm as 'backup' solution. Starting my own ssh-agent as a systemd service does not work, as the originally started ssh-agent is still the one used by my ssh connections and therefore the agent started via systemd is useless. My goal is to use Ansible only in the terminal. But I would like to have it work with the autostarted KeePass. The integration also obviously works when I start KeePassXC from my terminal or when I override the path manually. If I call echo $SSH_AUTH_SOCK in my terminal I get the correct path. Github Lab is an awesome way to discover your favorite. Now, KeePassXC and the ssh-agent are both autostarted by the same parent process (namely /sbin/init) and therefore the environment variable set by the ssh-agent is not available to KeePassXC. KeePassXC-Browser, Browser integration with KeePassXC-Browser SSHAgent, SSH agent integration. All you need to know about the integration is that is uses the environment variable SSH_AUTH_SOCK to get the path to the socket of the ssh-agent. From the Settings window, click the SSH Agent button, click the check-box for Enable SSH. I am using Manjaro with KDE, am on the current 5.9 Kernel and am trying to use the SSH-Agent integration of KeePassXC. The next step is to enable ssh-agent integration within KeePassXC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |