![]() We have already discussed the nomenclature for URLs and application names which has been modified accordingly. KP2A stands for keepass2Android, I have nothing against the app, on the contrary, but we need a generic nomenclature that everyone can use.I'm in favor of KP2A_ kind of prefixes instead of KPH ones (which are for special cases anyway). And this is the biggest part of the work because we have to make a pseudo language generic enough to accept the validations according to the types of fields. Credit Card type has "name", "number", "cvv", "expiry" Tell me if I'm wrong.įor each type a collection of well known/conventional custom fields. So it corresponds to one template, so a type = a template instance implementation in your nomenclature. So I had to raise this point, but if we all harmonize the format for a common UI to modify the templates, it's OK for custom attribute on an entry indicating what "type" of entry it was Keeping the old solution of one template per entry with a special group gives the advantage of not having to redo UI and the user is already used to manage the entries (it's also so much easier for the backward compatibility). OK for using the templates in JSON in the custom data, but we need to harmonize the implementation of the fields to define each template dynamically. This discussion is a good thing for a new #863 (comment) So I created a simplest pseudo language to overload it while waiting a normalization of the templates. But the format is really not great and not very flexible. I have already implemented the plugin code of KPEntryTemplates for backwards compatibility. KeePassX 0.4.I tried to reread the whole thread but I may have missed some information so don't hesitate if there are things I misunderstood, I'm just sharing my experience in implementing templates on the android application I'm working on.After KeePass/L became a cross platform application the name was not appropriate anymore and therefore, on 22 March 2006 it has been changed. Originally KeePassX was called KeePass/L for Linux since it was a port of Windows password manager Keepass Password Safe. This makes the use of that application even more favourable. KeePassX uses a database format that is compatible with KeePass Password Safe. Therefore the saved information can be considered as quite safe. The complete database is always encrypted either with AES (alias Rijndael) or Twofish encryption algorithm using a 256 bit key. Especially someone who generates passwords frequently will appreciate this feature. The password generator is very customizable, fast and easy to use. KeePassX offers a little utility for secure password generation. The integrated search function allows to search in a single group or the complete database. Furthermore the entries are sorted in groups, which are customizable as well. ![]() For a better management user-defined titles and icons can be specified for each single entry. user names, passwords, urls, attachments and comments in one single database. KeePassX saves many different information e.g. ![]() It has a light interface, is cross platform and published under the terms of the GNU General Public License. KeePassX is an application for people with extremly high demands on secure personal data management. Just in case you do not know what KeePassX is, here is a short description…
0 Comments
Leave a Reply. |