44 ms·
I just switched from MacPass to KeePassXC for the reason mentioned in release notes: it obsoletes the HTTP Connector and uses another mechanism. MacPass keeps u
by vetinari 9y ago
I just switched from MacPass to KeePassXC for the reason mentioned in release notes: it obsoletes the HTTP Connector and uses another mechanism. MacPass keeps using HTTP, and it is uknown, when it will do the same switch.
Given that I use multiple computers, and the extensions are synced, I want to use the same mechanism on all of them.
- scrollaway 9y agoDo you know the details of the differences between the old and the new mechanisms? All I see is a migration is required, but I used neither.
- vetinari 9y agoThe new mechanism uses Native Messaging[0], with the native application being keepassxc-proxy. The old one used HTTP, with the server (the password manager) listening on localhost. [0] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_messaging https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Na...