3 ms·
Just to be clear, you do realize that any pw manager that runs as a browser plugin has the same issue, right? If you want the convenience of being able to auto-
by anatolyrc 12y ago
Just to be clear, you do realize that any pw manager that runs as a browser plugin has the same issue, right? If you want the convenience of being able to auto-fill your passwords into the browser, that kind of limits your options.
- STRML 12y agoI'd definitely settle for an option where autofill is requested by the extension, but communicated via a bridge to a native application which can safely handle reprompts and cut off communication after a timeout.
- Buge 12y agoI don't think being a browser plugin has anything to do with it. If the problem is what mschulkind describes, then it can be fixed by changing the UI a little to have an autofill button while logged out, and to automatically log out after doing an autofill. I think the underlying issue, which KeePass also has, is that the entire database is encrypted. So to be able to search the database to see if a password exists, you need to decrypt the whole thing, including the passwords. If the passwords were each individually encrypted separately from the database, this could be fixed.
- STRML 12y agoI believe this is the same issue that 1Password had in the past, and a lot of users complained about exposed urls/titles in their storage format. I believe they now decrypt the urls & titles on startup in their plugins and keep them in memory, and only read the passwords at will, but I am not 100% on that.