This old horse can still fight, but should you care?
Although no longer actively developed, Gpass remains a fan favourite among the netizens. It stores the passwords in an encrypted file under the /.gpass directory, which is protected with a master password.
As it works only with an encrypted file, you can't create different databases. All login credentials must be stored in a single file. Another shortcoming is that it doesn't give you the option to search through the login credentials file. The single repository of login credentials can expand over time and, while the entries are arranged alphabetically, the inability to search through the list can become bothersome as it grows.
Gpass relies on the Blowfish encryption algorithm to make the password repository file unreadable. To add a new entry to the list, click the Add button and fill in the details in the Attribute Editor window. You can use the Type drop-down list to select either General or Folder.
Since it can't work with different files, you can create folders to easily manage your passwords; for example, a folder each for wikis, forums, blogs, and so on. Each folder can then have multiple entries.
Another useful feature is the password generator. In the Attribute Editor window, next to the Password field is the Generate button. You can use this to create a random password.
Login information for your bank accounts and other such sensitive information should not be trusted to a password manager no matter what its security feature set. With many easy-to-use tools still actively developed, there's little reason for you to use Gpass over any of them.
Price: Free under the GPL
Easy to install and use. But no database, and can't search or import