With KeePass Client v6.0.7
Jun 4, 2015
Warning For "Latest" Versions
Latest versions are intended for:
- early adopters
- evaluation of the product based on the latest feature set
- early access for planning of future deployments or providing Pleasant Solutions with feedback.
Latest versions are not ready for large mission-critical deployments, please use the most recent "Stable" version which has been tested much more thoroughly. Features in these Latest versions typically will make their way to Stable versions between 2 weeks and 3 months later.
- Improved database space efficiency for server with many file attachments
- Improved Logging message for the assignment of Comment Requirements to a Entry or Folder
- Various improvements in KeePass performance
- Fixed an issue that would result in database growing in size too much when Restoring Credentials with file attachments
- Fixed an issue where Syslog logging could not be disabled once configured
- Fixed an issue where Syslog logging would ignore the configured Facility
- Yubikey Two-Factor Authentication cannot be disabled once it has been enabled. This will be fixed in the next release.
- Clients that do not support the Usage Comment feature will not be able to perform actions that require comments. Make sure you also have the latest KeePass Client if you wish to use these features.
- KeePass Client for Password Server requires .NET Framework ≥ 4.5 (up from ≥ 4).
- Windows XP is no longer supported (it does not support .NET Framework 4.5).
- Nested AD/LDAP groups cannot be imported in Password Server Version 7.0.1 - 7.3.5.
- Internet Explorer 8 is no longer supported in Password Server Version ≥ 7.0.1.
- In Internet Explorer, The Password Server must be accessed using its fully qualified domain name.
- This is a significant release and Password Server may take a long time to start back up (only the first time) after the install completes as your database is upgraded. Remember to back up your database before beginning the upgrade as interrupting this process could leave the database in an unusable state.