v1.1.0-RC2

This release fixes a huge bug introduced in 1.1.0-RC, which just prevented OpenSSL from being used. See 1.1.0-RC for the release notes otherwise.

v1.1.0-RC

The main features of that new version are:

• Better support for upcoming PHP releases (which may not have mcrypt)
• Better preparation for future evolutions of KeePassPHP with a versioning of the API and of the stored password databases
• All string fields of databases entries can now be read through KeePassPHP
• Client code can now precisely select which data of a database can be stored internally by KeePassPHP (to avoid storing sensitive data)

Updating notes

There is some small API changes in 3ed3bc0, mainly impacting the class Entry (fields Entry::$title, Entry::$url and Entry::$username have been removed and can now be accessed through the method Entry::getStringField($key)).

v1.0.0-RC

This version contains fixes for all the bugs that I found since the beta. It is the most stable since the beginning of the project.
It can also use openssl if available instead of mcrypt, which is a actually a big improvement.

v1.0.0-beta

This version is a very deep refactoring of the previous one, and is more powerful, more flexible and easier to use as a library. The global architecture is done, the API will probably not change, but there may still be some bugs.

v0.0.2

This version fixes some important bugs in KeePassPHP, and adds the support for regular KeePass icons. But more importantly, it matches the last KeePassPHP-UI release (v0.0.2 as well) which had deep improvements.

v0.0.1

This version should work for basic usage, even though it was specifically designed to be used by the web UI (see KeePassPHP-UI), and is thus neither convenient, nor flexible, to use as a PHP library (and it still contains specific flaws).

I will start to do major refactoring of a lot ot things from now on, which may especially make KeePassPHP not compatible anymore with the current UI version. So I want to tag this point as the most usable version for now.