BPasswd is a strong password generator. It derives passwords from a master password and a usage-specific “salt”. Since BPasswd is aimed at the web, the “salt” is usually something site-specific such as “github”, “amazon”, “google”, etc. In other words, you get to reuse one (or a handful) of passwords, but end up with a unique password for each site. Best of all is that you don’t need to carry around some key file or trust a third-party service like you’d do with a password manager.
For a more generic introduction, do read the article.
BPasswd2 is available as a Firefox addon, a Chrome extension and a simple website. BPasswd2 is the new version of the original BPasswd addon that has been available for over a year now. It is fully backwards compatible, but offers more advanced settings which allow you to define per-site/salt options.
If you are looking for the web version, you can find an instance here.
The derived password is generated from an input master password and a “salt” (usually the site’s domain without the TLD). All three versions of BPasswd have a number of other settings that affect the generated password: “cost”, “generation/mapping method” and “maximum password length”. The first is described under the “How it works” section. The last one should be obvious - by default BPasswd generates 32-character (or 30-character if z85 is used) passwords, but some websites have password length limitations. This setting simply trims the password to whatever number of characters you tell it. The “generation/mapping method” option defines how the raw output of the bcrypt function is mapped back to ASCII characters:
The strongest passwords are the ones generated through the ‘z85’ mapping function, as they contain up to 85 different characters. However, some websites are really picky about which characters they allow in passwords, so ‘base64’ is the default and ‘conservative’ can be used for the pickiest of sites. ‘base64’ was the only mapping function supported and used in the first version of BPasswd.
The Firefox and Chrome versions can additionally store these site/salt-specific settings (and synchronize them using firefox sync/chrome sync). The web version uses HTML5 ‘localStorage’ (localStorage stores things locally in your browser, no server involved) to store site/salt-specific settings, but obviously cannot sync these settings.
This way you can for example store a setting for paypal, so it only ever generates passwords that are 20 characters long. Every time you generate a password for paypal, it’ll automatically use the saved settings - and it’ll let you know that it did, too.
A derived password for a specific site (salt) is generated as follows:
The ‘salt’ is hashed using HMAC-SHA-256 keyed with the SHA256-hashed ‘password’.
The input to bcrypt is this hashed salt, the original ‘password’ and the cost.
The output of bcrypt is a derived key of exactly 192 bits (24 bytes). This output is mapped back to ASCII characters through the mapping function defined by the generation method input.
The ‘cost’ input to bcrypt defines the number of iterations of the algorithm. The higher this value, the more compute intensive the key derivation is. The actual number of iterations is 2^(cost), so increasing the ‘cost’ by 1 roughly doubles the time it takes to derive a key. BPasswd (and BPasswd2) use a default cost of ‘6’, i.e. 64 iterations.
As mentioned earlier, the result of this process is not a strong crytopgrahic key due to the salt not being random. However, it is more than appropriate as a password.