Juan Porta

Hello, I wanted to let you know that I wrote OneVault, a plugin for KeePass 2 to import 1Password OPVault bundles. This plugin is similar to OnePIF, another plugin I wrote to import 1PIF files. Both provide the same functionality and can import the same item types so, why another plugin? Mostly because of: - Security: 1PIF format stores information unencrypted, while OPVault is almost entirely encrypted. Using the new OneVault plugin you can import vaults without temporarily storing all your secrets...

You're right. Though String.Compare is not aimed at checking if two strings are equal (that's what String.Equals is for) it lets you specify not only the culture used for the comparison but also to ignore diacritics and casing in one simple call. So calling String.Compare("Grüßen", "grussen", CultureInfo.CurrentCulture, CompareOptions.IgnoreNonSpace | CompareOptions.IgnoreCase) will return 0 (meaning the two strings are considered equal) which is what the OP asked for. Regards

You're right. Though String.Compare is not aimed at checking if two strings are equal (that's what String.Equals is for) it lets you specify not only the culture used for the comparison but also to ignore diacritics and casing in one simple call. So calling String.Comapre("Grüßen", "grussen", CultureInfo.CurrentCulture, CompareOptions.IgnoreNonSpace | CompareOptions.IgnoreCase) will return 0 (meaning the two strings are considered equal) which is what the OP asked for. Regards

Well this is certainly not a simple matter, but I think there are some approaches that might work in most cases. I'm no expert in Unicode and character encodings so I'll probably use the wrong terms in the following paragraphs, sorry for that. For the diacritics one solution could be normalizing the string to its Unicode canonical decomposition (e.g. the single č character is decomposed as the character c plus the caron diacritic) and then removing all diacritic characters from the resulting normalized...

Of course, I overlooked the reference to KeePass as an indication of a real plugin DLL! I was considering loading the assembles (and examining some info) as a solution because KeePass was already doing it. But as you pointed out, filtering them before even loading is a far better solution. Thank you very much for looking into and fixing this so quick! Regards

I wrote a plugin which makes use of localized resources. While testing, I found that placing the plugin DLL with its localization satellite DLLs in the corresponding Plugins directory made KeePass to complain (once for each culture) that the plugin is incompatible.[1] I found a workaroud placing the plugin in the main app dir instead of the Plugins dir. Since the PluginManager only performs a recursive scan in the Plugins dir but only searches the top level for the main app dir, the satellite DLLs...

Thank you very much for adding it, Dominik. It's my pleasure to contribute something to the KeePass community. I'm still not a user, but will be soon for sure! Regards, Juan

Hello, I wanted to let you know that there's yet another 1Password Interchange Format (1pif) import plugin for KeePass 2. Why another 1P import plugin? The "1PW & 1Password Pro CSV" plugin bundled with the main KeePass distribution imports 1P data from CSV files, which do not contain user-defined custom fields and many other pieces of data present in 1P vaults. On the other hand, 1P2KeePass imports data from 1pif files and works great, but lacks support for many of 1P item types and custom fields....