Skip to content

Docs and code conflicting about age.ssh-key-path; cannot make gopass not read identities from ~/.ssh #3522

Closed

Description

@quite

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

Activity

  1. dominikschulz commented on Aug 7, 2026

    @dominikschulz
    Member

    @quite Yes, that makes sense. If users don't want gopass to access .ssh there should be an easy way (maybe even the default) to do that.

  2. quite commented on Aug 7, 2026

    @quite
    ContributorAuthor

    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).

    How does that sound?

  3. dominikschulz commented on Aug 10, 2026

    @dominikschulz
    Member

    @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 😏

  4. added 7 commits that reference this issue on Aug 11, 2026
    8573e40
    5b9837e
    7aaab8e
    bc3715a
    0e7cd27
    89e3c9f
    ff4ab1d
  5. added a commit that references this issue on Aug 21, 2026
    19e4aa4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ageage-encryption.org backendbugDefects

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      ⌂ 换网址