Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
4 years ago[Linux] Use $XDG_RUNTIME_DIR instead of $HOME/.1password?
I like to try (although not very successfully) to keep my home directory clean of unnecessary dotfiles. While this is a very cool feature, I think it makes more sense to keep the socket in $XDG_RUNT...
1P_Phil
Moderator
2 months agoHi ragectl ,
Thanks for bumping this. I'll re-share this with the team.
Just to confirm, you are looking for a way to personalize the "~/.1password/" directory location from "~" to potentially the env's $XDG_RUNTIME_DIR or elsewhere.
Let me know if I got that wrong.
Cheers,
Phil & Team
ragectl
2 months agoOccasional Contributor
Yes, please.
I checked the documentation and even tested this on current BETA release for Linux and there is no documented way to move this SSH agent socket file out of ~/.1password/ directory.
As the other comment noted, this value in the SSH config file should be supported:
${XDG_RUNTIME_DIR}/1Password-ssh-agent.sockssh_config shows that environment variables are supported for IdentityAgent in modern releases:
Arguments to IdentityAgent may use the tilde syntax to refer to a user's home directory, the tokens described in the “TOKENS” section and environment variables as described in the “ENVIRONMENT VARIABLES” section
Which allows the SSH config file to be set like this:
Host *
IdentityAgent ${XDG_RUNTIME_DIR}/1Password-ssh-agent.sockThat would put the SSH agent socket file in the same directory the browser integration socket file is already using:
${XDG_RUNTIME_DIR}/1Password-BrowserSupport.sockSo it's clear this directory is supported by 1Password on Linux, just needs to be updated for configuration of SSH Agent socket file.
Ideally, XDG_RUNTIME_DIR would be used by default, with a fallback to the current location.
Alternatively, less user-friendly would be to allow us to specify the socket file location in the SSH Agent config file ~/.config/1Password/ssh/agent.toml