You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docs and code conflicting about age.ssh-key-path; cannot make gopass not read identities from ~/.ssh #3522
I think I am running into #3507 which is indeed a flaw in itself. But I was originally trying to make gopass not read any sshkeys from ~/.ssh at all; i have all sorts of things there that I don't want gopass to access at all.
The docs in https://github.com/gopasspw/gopass/blob/master/docs/config.md says that age.ssh-key-path (only) will be used if set, otherwise ~/.ssh will be used. So I was trying to set age.ssh-key-path to ~/.non-existant, to make gopass not load any SSH identities, but that did not work. Because the code uses both dirs to find SSH identities!
I really think there should be a way to not have gopass access ~/.ssh -- I think making it to what the docs says would make sense. Or possibly some other way to turn off SSH identities entirely. What do you say @dominikschulz
Ok good. I'm thinking to add a --age-sshkeys (and age.sshkeys for config; no envvar). Default false, so loading keys (identities) from ~/.ssh/ has to be enabled explicitly. This is a breaking change for users, but we're all experimental here right.
The age.ssh-keys-path will be left as is. If it is set, identities there will be loaded in addition to any from ~/.ssh/ (if that is at all enabled by user).
@quite That sounds good. I'm still considering the age backend experimental and as long as we call that breaking change out clearly in the release notes we should be good. Of course https://xkcd.com/1172/ applies 😏
Activity
dominikschulz commentedon Aug 7, 2026
@quite Yes, that makes sense. If users don't want gopass to access
.sshthere should be an easy way (maybe even the default) to do that.quite commentedon Aug 7, 2026
Ok good. I'm thinking to add a
--age-sshkeys(andage.sshkeysfor config; no envvar). Defaultfalse, so loading keys (identities) from~/.ssh/has to be enabled explicitly. This is a breaking change for users, but we're all experimental here right.The
age.ssh-keys-pathwill be left as is. If it is set, identities there will be loaded in addition to any from~/.ssh/(if that is at all enabled by user).How does that sound?
dominikschulz commentedon Aug 10, 2026
@quite That sounds good. I'm still considering the age backend experimental and as long as we call that breaking change out clearly in the release notes we should be good. Of course https://xkcd.com/1172/ applies 😏
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh
fix: require --age-sshkeys (or age.sshkeys config) to access ~/.ssh (#…