Read the changelog for the latest features and fixes.
- Using pass or git and gpg2 directly
- Cross platform: Linux, BSD, OS X and Windows
- Using native widgets and iconography where possible
- Reading pass password stores
- Decrypting and displaying the password and related info
- Editing and adding of passwords and information
- Updating to and from a git repository
- Per-folder user selection for multi recipient encryption
- Configuration options for backends and executable/folder locations
- Copying password to clipboard
- Configurable shoulder surfing protection options
- Easy onboarding for new users
- Experimental WebDAV support
- Much more
pacman -S qtpass
OpenSUSE & Fedora
yum install qtpass
dnf install qtpass
Debian, Ubuntu and derivates like Kali & Raspbian
apt-get install qtpass
emerge -atv qtpass
pkg install qtpass
cd /usr/ports/sysutils/qtpass/ && make install clean
Latest stable on the releases page, latest build via AppVeyor.
choco install qtpass
Latest stable on the releases page, latest build via AnneJan.
Via Homebrew Cask
brew cask install qtpass
- QtPass requires Qt5.
- The Linguist package is required to compile the translations.
- For use of the fallback icons the SVG library is required.
On most *nix systems all you need is:
qmake && make && make install
On Mac OS X:
brew install qt5
brew link --force qt5
qmake && make && macdeployqt QtPass.app
Currently seems to only work with MacGPG2
Using this program will not magically keep your passwords secure against
compromised computers even if you use it in combination with a smartcard.
It does protect future and changed passwords though against anyone with access to
your password store only but not your keys.
Used with a smartcard it also protects against anyone just monitoring/copying
all files/keystrokes on that machine and such an attacker would only gain access
to the passwords you actually use.
Once you plug in your smartcard and enter your PIN (or due to CVE-2015-3298
even without your PIN) all your passwords available to the machine can be
decrypted by it, if there is malicious software targeted specifically against
it installed (or at least one that knows how to use a smartcard).
To get better protection out of use with a smartcard even against a targeted
attack I can think of at least two options:
- The smartcard must require explicit confirmation for each decryption operation.
Or if it just provides a counter for decrypted data you could at least notice
an attack afterwards, though at quite some effort on your part.
- Use a different smartcard for each (group of) key.
- If using a YubiKey or U2F module or similar that requires a "button" press for
other authentication methods you can use one OTP/U2F enabled WebDAV account per
password (or groups of passwords) as a quite inconvenient workaround.
Unfortunately I do not know of any WebDAV service with OTP support except ownCloud
(so you would have to run your own server).
- Plugins based on key, format is same as password file.
- Colour coding folders (possibly disabling folders you can't decrypt).
- Optional table view of decrypted folder contents.
- Opening of (basic auth) urls in default browser? Possibly with helper plugin for filling out forms?
- WebDAV (configuration) support.
- Other forms of remote storage that allows for accountability / auditing (web API to retreive the .gpg files)?
- Refactoring MainWindow class.
Can't save a password
- Filtering (searching) breaks the tree/model sometimes.
- On Mac OS X only the gpgtools MacGPG2 version works with passphrase or PIN.
I have an issue with GNOME keyring
- Is folder initialised? Easiest way is to use the [Users] button and make sure you can encrypt for someone (eg. yourself)
- Are you using git? If not, make sure it is switched off.
- Disable GNOME keyring
- Create a
Also, the following is useful to add to your .bashrc if you are using Yubikey NEO on Ubuntu:
Can I import from KeePass, LastPass or X?
Are there more frequently asked questions?
Where can I ask for help?
Read up on recent changes
# OpenPGP applet support for YubiKey NEO
if [ ! -f /tmp/gpg-agent.env ]; then
eval $(gpg-agent --daemon --enable-ssh-support > /tmp/gpg-agent.env);