| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
The patch no longer applies because some of the imports got changed in
the context of the diff.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 7b8164be35c9d82d6e7389a407150a9128f7fb0c.
From the upstream changelog:
> This is an important bugfix release that should resolve several
> outstanding issues and concerns. Since 1.10.0 was released was engaged
> in a lot of discussions and realized that compatibility is more
> important than we first thought. So we're rolling back some breaking
> changes and revise some parts of our roadmap. We will strive to remain
> compatible with other password store implementations - but remember
> this is a goal, not a promise. This means we'll continue using
> compatible secrets formats as well as GPG and Git.
As mentioned in the original commit, I'm still not entirely convinced
that my use case has a future with gopass, their decision to roll back
some of the breaking changes at least makes it possible for me to
upgrade to the latest upstream version without the fear of being locked
in into some gopass-specific format.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version 1.10.X switches the default to new MIME-based format which
breaks interoperability with pass and other implementations.
I'd gladly switch to that format, but the 1.10.0 changelog also
announces plans to remove support for GnuPG and Git in the long term:
> The goal is to remove the support for multiple backends and any
> external dependencies, including git and gpg binaries.
GnuPG and Git support is the reason why I started using pass and
ultimately switched to gopass. If the latter stops being a viable
password manager, switching back to pass will be much harder with the
new MIME format.
There is also an upstream issue[1] about this and while I haven't read
through *all* the comments, other people seem to have similar reasons
for switching to gopass.
So far however I'm not convinced that my use case will have a future
with gopass, so I'll stay at 1.9.x until I've had the time to properly
research other options or maybe even stay with gopass (and go all-in
with the new MIME format).
[1]: https://github.com/gopasspw/gopass/issues/1365
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
With the switch to a proper Unicode capable font, we no longer need to
patch gopass and simply can now enjoy a proper tree view and also one
less patch to maintain.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
The import list of list.go has changed upstream, so the rebase of this
patch doesn't change anything in its functionality but just makes sure
that it applies against gopass version 1.9.0.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
| |
The patches are basically the same but only the files were moved to a
different place in the upstream repository.
Tested building and execution.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
I only want gopass to use ASCII symbols. This is something I already
hated in pass, but I never changed it. By switching to gopass now, it's
a great opportunity to change it.
Second, I use "less -R" as a pager, which supports color so there really
is no need to disable colors before piping it to my pager.
Signed-off-by: aszlig <aszlig@nix.build>
|
