I hope to finish the work in v1.18, but as always, no guarantees. connect to a KeeWeb tab in browser and exchange encrypted data.seamless work with several databases being opened at the same timeįor now it can't do much, however it already can:.better security, for example, it won't store database tokens in a plaintext file.support for web mode, when KeeWeb is opened in a browser tab, without installed native apps.compared to KeePassXC-browser, this extension will provide:.the UI will be minimalistic, think of it as auto-type for browser done right.however, the extension won't be able to connect to KeePassXC (in theory, that's possible, but I don't think there's any demand for it).there will be an option to switch to KeePassXC-browser in KeeWeb, but by default it will offer our extension.KeeWeb will be able to work with both KeePassXC-browser, as well as our own extension.it will use KeePassXC-browser protocol with backward-compatible additions:.we'll for sure have our own extension developed from scratch.I'd like to share some decisions and progress: Would this extension solve your day-to-day needs or something is missing? What do you think? Is there demand for such extension? any other UI "injected" into websites: just don't do it! it looks and behaves not as it shouldįor example, we can start with something like this: icons, buttons, different forms of auto-completion, etc.saving fields back to KeeWeb: again the absence of standards and APIs makes it complicated.auto-fill without user interaction: this is a product in itself that requires dedication and careful development due to vulnerabilities it can introduce and flexibility of HTML forms.configurable shortcuts for common actions.trigger the auto-type selection pop-up if a matching entry can't be found automatically.insert username / password / both / auto / otp / other field.The extension can provide the bare minimum that can be expected from it: Own extension doesn't seem to be hard to implement, assuming that we can avoid overloading it with features. It will give us a possibility to connect to KeePassXC-browser, as well as build our own extension based on it. The protocol used in KeePassXC-browser called keepassxc-protocol can be used by different extensions, so we should support it in KeeWeb. It doesn't work with Safari and the maintainers don't seem to be enthusiastic about it.There's an ethical dilemma regarding overwriting the application it opens, I would prefer describing it in the app but leave the choice to the user, so that this option is not offered by default but there's a possibility to do so with a bit of configuration.There's a lot of critique about its security and I see that the browser extensions are not actively developed. KeePassHttp or KeeWebHttp seems to be going nowhere, supporting it doesn't make sense anymore. Retrieved September 2, 2022.Since people here may find it interesting, I'll share my thoughts about supporting browser extensions in KeeWeb. ^ "KeePassXC-Browser – Get this Extension for Firefox (en-US)".^ "KeePassXC-Browser", KeePassXC, Aug, retrieved September 2, 2022. ![]() The most important reason people chose KeePassXC is: Free. In the question What is the best cross-platform password manager KeePassXC is ranked 1st while KeePass is ranked 3rd. ^ "FreshPorts - security/keepassxc: KeePass Cross-platform Community Edition". When comparing KeePass vs KeePassXC, the Slant community recommends KeePassXC for most people. ![]()
0 Comments
Leave a Reply. |