An easy-to-use password manager for Windows, compatible with pass.
pw.exe
application is now additionally supplied. Like pass-winmenu
, it expects a pass-winmenu.yaml
configuration file telling it where to find passwords and how to decrypt them. It is mainly intended for scripting, as a simple alternative to installing pass
on Windows.Replace
button allowing you to easily replace the password in a file with a newly generated one (#122)..gpg
extension mistakenly being included in the $filename
variable (#120)\n
as line terminator in edited password files (#123)Thanks to everyone who submitted issues, and especially @scerzh for submitting several PR's for this release.
Starting from the next major version (1.14), pass-winmenu will be retargeted to .NET 6. Along with this, support for Windows 8.1 and older can no longer be guaranteed, and future releases will require you to have the .NET Desktop Runtime 6.0 installed. If you expect to run into problems as a result of this change, please let me know by opening an issue.
gpg-agent.conf
pinentry-fix
feature, which was meant to work around a bug GPG, where the pinentry window would not appear in the foreground. This workaround only sometimes managed to fix the issue, but it often still failed. If you run into issues with pinentry not appearing in the foreground, the recommended solution is to install Gpg4win instead, in which this issue is not present.TOTP: <secret>
You can also directly copy an otpauth
URL.
OTPAUTH: otpauth://otp/account?secret=<secret>
To generate a TOTP code, select generate TOTP code
in the right-click menu of the notification area icon, or create a hotkey binding using generate-totp-code
as action name.style
configuration key) are now consistently parsed using a dot as the decimal separator. Previously, the culture-specific separator was used instead.user.name
and/or user.email
git configuration variables are not set (#100).git.ssh-path
if the GIT_SSH
environment variable is also set (#98)More Options -> Re-Encrypt Password Store
, and choosing a path to re-encrypt.pass
allows the use of the PASSWORD_STORE_KEY
environment variable to override the recipients specified in .gpg-id
when set. Pass-winmenu now also honours this variable (#86).gpg.exe
when passwords are encrypted or decrypted. Take a look at the default configuration file to see how you can configure these. (#86).dead-keys
option has become redundant and can be removed from the configuration file (#80).Starting from this release, the default configuration file location will be the same directory as the one pass-winmenu.exe
is located in.
In previous versions, the configuration file location was set to the current working directory.
In the vast majority of cases, these two locations will point to the same directory, but in certain cases, they may differ. For instance, if you start pass-winmenu via a shortcut and modify the Start in:
field of the shortcut, the configuration file would formerly be created in the directory specified there, but would now be created next to pass-winmenu.exe
.
If you'd like the configuration file to be located in a different directory, you can make use of the newly-added feature that lets you modify the configuration file location (see below).
git fetch
will now be run periodically, once an hour by default. The interval can be changed (or the feature can be disabled completely) in the configuration file. See here for details.git config commit.gpgsign
is true
) (#69).sync-mode
(auto
), this will automatically make use of native-git
if it's available. On new installations, this will be the default (#68).--config-file <path-to-file>
as an argument to pass-winmenu. Probably the easiest way to do this is by creating a shortcut to pass-winmenu.exe
, and adding the argument to the Target:
field of the shortcut (#60, #61).username-detection: line-number
(#66)..yaml
files.The current implementation of the GPG agent configuration file updater (which is enabled when you have allow-config-management
set to true
) has a bug, causing it to remove any non-configuration (comment) lines from your configuration file while updating it.
As v1.10 is still some time away, and this bug is too significant to leave unresolved until then, this release bridges the gap.