Releases: ttyridal/masterpassword-firefox
v2.0.1 final
The 2.0.1 release includes bugfixes found since the 2.0.0 release and a couple of new features.
- You can now configure a timeout, at which the master key have to be typed again.
- Import of .mpsites from iOS devices is fixed.
- Dropdown for multiple sites didn't display before reload is fixed.
- Fixed issue where some sites didn't recognise the auto-fill of password (protonmail.ch and others using observer pattern)
- Fixed issue where wrong password was not detected and warned.
2.0.1 pre release
Changes since 2.0.1pre2:
Fixed bugs:
- default password strength was not used for new sites (Issue #23)
- Password entry was not detected by some sites (accounts.firefox.com) (Issue #19)
New features:
- Option to forget master password within a time limit. (Issue #22)
In addition this version tries to improve situations where username and site settings apparently disappears for unknown reasons. (Issue #24)
2.0.1 pre release
v2.0 Final
New in this release:
- Optionally save your masterpassword in the key vault of your OS (see readme for details and security implications)
- Multiprocess firefox ready (firefox version >= 43)
- Exported .mpsites files will now have the minumum algorithm version required, instead of always using version 3 (this should help those how sync with iOS app)
- Visually emphasize if password changes from previous login (helps detect mistyping)
- Check master password hash on import
- Notify when importing .mpsites with incompatible algorithm version
- Support for Firefox versions older than 38 dropped.
Fixed bugs:
- Password never calculated on some configurations/systems (library not loaded in time)
- Handle site names with multiple '@' (ie my@[email protected])
- Include master password hash in export file
v2.0 Release candidate 2
new in RC2:
When exporting to .mpsites file the addon will now announce the minimum viable algorithm version in addition to some bugfixes in the export code. This will enable users of the masterpassword app for iOS and osX to import the file
If you mistype your password or login name there is now a clear indication of this.
When importing a .mpsites file, the addon will now verify algorithm version compatibility, and that the username and password used to generate the file matches the user name and password used in the app.
v2.0 Release candidate
new features:
- optionally keep master password in OS password store Kwallet / GNOME Keyring / OSX Keychain / Windows Password vault
- e10s / multiprocess Firefox ready (Firefox version >= 43)
bug fixes:
- wait for crypto library to load (fix issue where site password is not generated)
- handle full email addresses as username when importing .mpsites file
v2.0 preview 2
new features:
- optionally keep master password in Kwallet / GNOME Keyring
- e10s / multiprocess Firefox ready (Firefox version >= 43)
bug fixes:
- wait for crypto library to load (fix issue where site password is not generated)
- handle full email addresses as username when importing .mpsites file
This is a pre-release, Please report any issues you might experience
Peak preview of KWallet / GNOME Keyring integration
Title says it all.. If you do not very much desire the KWallet / GNOME Keyring integration and are willing to accept that things might not work as expected you are highly encouraged to use the v1.0 release instead.
Please also report any problems you might have.
To enable kwallet / keyring select your option in the addon preferences. Gnome and KSecretService (next generation Kwallet) uses a standardised api called "Secret Services"
Version 1.0 final
- Minor visual update
- Associate a login name with the site. It will currently not auto fill login forms, but it is strongly suggested to not use this field for random notes.
- Configurable default password strength
- Verify master key field. Gives you a string in the ui calculated from your master key. (thanks to johanneslotz for contributing)
V1.0 beta 1
New features:
- Verify master password. Gives you a visual clue if you've typed your master password correctly (thanks to johanneslotz for contributing!)
- Store login name (or any text) associated with the site you're visiting. (it will not auto fill, but might in the future). The login name have no influence on the password generated.
- A tiny visual cleanup.