The slightly more awesome standard unix password manager for teams
MIT License
Bot releases are hidden (Show)
Published by gopass-releaser over 3 years ago
Published by gopass-releaser over 3 years ago
WARNING: The self updater does not support updating from 1.11.0 to 1.12.0. Our
release infrastructure does not support the key type used in 1.11.0.
NOTE: This release drops the integrations that were moved to their own repos,
i.e. git-credential-gopass
, gopass-hibp
, gopass-jsonapi
and
gopass-summon-provider
.
We have implemented proper release signing and verification for the self
updater and brought it back.
Published by gopass-releaser over 3 years ago
Published by dominikschulz almost 4 years ago
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.
Notice the Windows support should have been significantly improved.
Notice the Mime type was removed. Run gopass fsck --decrypt
to detect
leftover Mime secrets. They won't be converted automatically for now but if you
edit them they can be converted into standard plain or key-value secrets.
Published by dominikschulz about 4 years ago
[BUGFIX] Fix the Makefile
[BUGFIX] Remove misleading config error message
[BUGFIX] Re-use existing root store
[BUGFIX] Use standard Unix directories on MacOS
Published by dominikschulz about 4 years ago
WARNING: This release contains a few breaking changes as well as necessary
packaging changes.
This release is building the foundation for an eventual 2.0 release
which will drop many legacy features and significantly shrink the
codebase to ensure long term maintainability. The goal is to remove
the support for multiple backends and any external dependencies,
including git
and gpg
binaries. By default the tool should be easy to use,
secure and modern. We will still support our flagship use cases,
like working in teams. Also gopass might eventually move to an
fully encrypted backend where we don't leak information through
filenames.
Any gopass 1.x release should still be compatible with any
password store implementation (possibly with some caveats).
Beyond that we plan to drop any compatibility goals.
If you are using different Password Store implementations to access your
secrets, e.g. on mobile devices, you might want to run gopass config mime false
before performing any kind of write operation on the password store. Otherwise
mutated secrets will be written using the new native gopass MIME format and
might not be readable from other implementations.
This release adds documentation for all supported subcommands in the docs/commands
folder and starts define our core use cases in the docs/usecases
folder.
Please note that the command documentation also serves as a specification on
how these commands are supposed to operate.
Note: We have accumulated too many changes so we've decided to skip the 1.9.3
release and issue the first release of the 1.10. series.
Note to package maintainers: This release adds additional binaries which should
be included in any binary re-distribution of gopass.
Published by dominikschulz about 4 years ago
WARNING: This release contains a few breaking changes as well as necessary
packaging changes.
This release is building the foundation for an eventual 2.0 release
which will drop many legacy features and significantly shrink the
codebase to ensure long term maintainability. The goal is to remove
the support for multiple backends and any external dependencies,
including git
and gpg
binaries. By default the tool should be easy to use,
secure and modern. We will still support our flagship use cases,
like working in teams. Also gopass might eventually move to an
fully encrypted backend where we don't leak information through
filenames.
Any gopass 1.x release should still be compatible with any
password store implementation (possibly with some caveats).
Beyond that we plan to drop any compatibility goals.
If you are using different Password Store implementations to access your
secrets, e.g. on mobile devices, you might want to run gopass config mime false
before performing any kind of write operation on the password store. Otherwise
mutated secrets will be written using the new native gopass MIME format and
might not be readable from other implementations.
This release adds documentation for all supported subcommands in the docs/commands
folder and starts define our core use cases in the docs/usecases
folder.
Please note that the command documentation also serves as a specification on
how these commands are supposed to operate.
Note: We have accumulated too many changes so we've decided to skip the 1.9.3
release and issue the first release of the 1.10. series.
Note to package maintainers: This release adds additional binaries which should
be included in any binary re-distribution of gopass.
Published by dominikschulz about 4 years ago
Note: We have accumulated too many changes so we've decided to skip the 1.9.3
release and issue the first release of the 1.10. series.
Published by dominikschulz about 4 years ago
This release adds additional binaries which should be included in
any binary re-distribution of gopass.
Published by dominikschulz over 4 years ago
WARNING: This release contains a few breaking changes.
This release is building the foundation for an eventual 2.0 release
which will drop many legacy features and significantly shrink the
codebase to ensure long term maintainability. The goal is to remove
the support for multiple backends and any external dependencies,
including git and gpg. By default the tool should be easy to use,
secure and modern. We will still support our flagship use cases,
like working in teams. Also gopass will eventually move to an
fully encrypted backend where we don't leak information through
filenames.
Any gopass 1.x release should still be compatible with any
password store implementation (possibly with some caveats).
Beyond that we plan to drop any compatibility goals.
Published by dominikschulz over 4 years ago
Published by dominikschulz over 4 years ago
Published by dominikschulz over 4 years ago
Published by dominikschulz about 5 years ago
Published by dominikschulz over 5 years ago
Published by dominikschulz almost 6 years ago
Published by dominikschulz almost 6 years ago
Published by dominikschulz over 6 years ago
Published by dominikschulz over 6 years ago
Published by dominikschulz over 6 years ago