MùPùF.org

After one year and more than 300 commits, PPassKeeper 1.0 beta 2 has finally been released !

What is PPassKeeper ?

PPasskeeper is my main personal project. It is a library that intends to create a portable way of storing sensitive information, such as passwords or private keys, into a safe place. In order to be portable and flexible, the library allows third-party developers to improve it by creating more plugins that can be free (as in freedom) or proprietary.

The goals of this project is to :

• Provide a common interface for desktops and operating systems to access secure password storages
• Be modular
• Allow third-party developers to easily create new modules
• Be backwards compatible

This project is developed under the LGPL v2.0 or later license.

What has changed since the beta 1 ?

Well, a lot of things have changed. As a summary, I can tell that it is way more mature, it is now thread-safe, has a better API/ABI, supports blobs, has support for the Gnome-Keyring, initial support for modules parameters, created unit tests, switched to CMake and fixes a lot of bugs !

PPassKeeper, my main project, intends to become a plugin-based portable way to store passwords in a secure and easy fashion.

The API for getting and setting passwords is quite simple and is good for modules like the Gnome-Keyring or the KWallet but there are some cases where this simplicity is just disastrous. For instance, for modules like WebDAV or LDAP (these modules have not been coded yet). In fact, there are loads of parameters needed by some modules and the only way they had was to use configuration files.

This time is over as PPassKeeper now provides a way to handle parameters !

Would you fancy a C-container that can hold a string, an integer or a float ?

There are some cases where you need, for instance, to return a value that could be of any type. This case just happened to me when I needed to handle parameters for PPassKeeper modules.

Here is my fully documented and explained solution, all written in C.