Resources
Identity Use Cases & Scenarios.
FIDIS Deliverables.
Identity of Identity.
Interoperability.
Profiling.
Forensic Implications.
HighTechID.
D3.1: Overview on IMS.
D3.2: A study on PKI and biometrics.
D3.3: Study on Mobile Identity Management.
D3.5: Workshop on ID-Documents.
D3.6: Study on ID Documents.
D3.7: A Structured Collection on RFID Literature.
D3.8: Study on protocols with respect to identity and identification – an insight on network protocols and privacy-aware communication.
D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management.
D3.10: Biometrics in identity management.
D3.11: Report on the Maintenance of the IMS Database.
D3.15: Report on the Maintenance of the ISM Database.
D3.17: Identity Management Systems – recent developments.
D12.1: Integrated Workshop on Emerging AmI Technologies.
D12.2: Study on Emerging AmI Technologies.
D12.3: A Holistic Privacy Framework for RFID Applications.
D12.4: Integrated Workshop on Emerging AmI.
D12.5: Use cases and scenarios of emerging technologies.
D12.6: A Study on ICT Implants.
D12.7: Identity-related Crime in Europe – Big Problem or Big Hype?.
D12.10: Normality Mining: Results from a Tracking Study.
Privacy and legal-social content.
Mobility and Identity.
Other.
IDIS Journal.
FIDIS Interactive.
Press & Events.
In-House Journal.
Booklets
Identity in a Networked World.
Identity R/Evolution.
KeePass Password Safe feedback
Keepass Identity Management System
Verification of data – Instructions
Please indicate with a Yes/No in the respective field of the following table the correctness / completeness of the data held in our database. If you find that the data is not correct and/or complete, please proceed with making the appropriate corrections / additions by appropriately filling in the next field (“Correction / Completion”).
For a description / definition of each field, you can refer at Table B.
TABLE A – Verification of Data | ||||
Data held in database | Yes/No | Correction / Completion | ||
Evaluation of IMS | ||||
Evaluator: | Christian Krause |
|
| |
Organisation: | ICCP |
|
| |
Date of evaluation: | 06-Jun-2005 |
|
| |
Identification of IMS | ||||
Sources of information: | http://keepass.sourceforge.net | Yes |
| |
Version: | 1.0 | No | 1.05 is the latest version. | |
Manufacturer: | Dominik Reichl | Yes |
| |
Nature: | private | Yes |
| |
Country: | Germany | Yes |
| |
Regions: | Global | Yes |
| |
Language: | CZECH,DANISH,DUTCH,ENGLISH,ESTONIAN,FRENCH,GERMAN,HUNGARIAN,ITALIAN,POLISH,PORTUGUESE,SLOVAK,SPANISH | Yes | Also in Bulgarian, Catalan, Finnish, Greek, Hebrew, Japanese, Korean, Lithuanian, Macedonian, Norwegian, Russian, Chinese, Swedish, Turkish, Ukrainian | |
State: | Available | Yes |
| |
Open/Closed: | Open IMS: the identities work with several systems or applications. | Yes |
| |
Platform & Environment | ||||
Requirements: | MS Windows 95 or higher | Yes |
| |
Number of users: | 237365 Downloads in May 2005 | No | 860.442 downloads up to July 2006 | |
Standards: | Interoperability is mainly achieved via clipboard-functions of Windows Operating System. This Software is OpenSource, so it can theoretically ported to other systems. | Yes | Interoperability also through Auto-Type, Drag-and-Drop and automatic form filling. | |
Description of Server - Side components: | n.a. | Yes |
| |
Description of methods: | KeePass is a password manager with an AES/Twofish encrypted database. | Yes |
| |
Descriptor of Client - | KeePass | Yes |
| |
Seals: | No | Yes |
| |
Which seal: |
| Yes |
| |
Third party: | no | Yes |
| |
Which third party: |
| Yes |
| |
Features: | Users can store passwords and add meta-data such as URLs, expiry-dates and comments. Passwords are copied to clipboard via double-click and are deleted from clipboard automatically after ten seconds. | Yes |
| |
Screenshot picture: | Yes |
| ||
Flowchart: | Yes |
| ||
Cost | ||||
Price: | 0 | Yes |
| |
Comment to the Cost: |
| Yes |
| |
Type & Class of IMS | ||||
Type of IMS: | Type 3: IMS for user-controlled context-dependent role and pseudonym management. | Yes |
| |
Class of IMS: | Class 1: Pure IMS which main objective is to support or implement identity management functionality. | Yes |
| |
Functionality: |
| Yes |
| |
Suggestions: |
| Yes |
|
11 / 15 |