sudoforge

quote @seatedscribe: >`@bddenhartog` having a PIN unrelated to the master password reduces the attack surface. Should the PIN remain the same from session to session, or is it to be...

``` ➜ ./gopass foo foo.com/potato foo/apple foo/orange foo/bar/baz foo/bar/quux ➜ git log -1 --format='%H' 88e589a1d67260f3aff6ba4ffcafdf709d3ba6d9 ➜ ./gopass version gopass 1.9.0-git+HEAD go1.14.2 linux amd64 - gpg 2.2.20 - git 2.26.2 -...

(The above works the same for subcommands, e.g. `./gopass generate foo`)

If the _intent_ is to only show the first level after the pattern, then it's bugged (although I'm unclear on whether or not this matches with what the issue author...

I wouldn't necessarily label this as a bug, it's really a feature request. I have an idea on how to handle this cleanly via Make, and will try to send...

I updated the description and title of this issue for additional clarity. Yes, the configuration for bridges is read from the local configuration, and credentials are read from global. This...

Also, note that there is a bug with the way credentials are read from the global configuration. If my global configuration contains a block like: ``` [include] path = ~/.gitconfig.foo...

Yeah, if you have the follow file structure: **`~/.gitconfig`** ``` [include] path = "~/.gitconfig.local" ``` **`~/.gitconfig.local`** ``` [foo] bar = "baz" ``` then `git config --get foo.bar` returns `baz` as...

`git-bug` should probably not care about where the credentials are coming from and rely upon Git's configuration loading by simply calling: ``` git config --get ``` instead of explicitly calling...

I don't have time to familiarize myself with the codebase today, but this is a fairly trivial patch (if you approve of it) and I'd be happy to take care...