![]() The benefits of a password manager include: KeePassXC is recommended by the EFF in their Surveillance Self-Defense guide and it is considered a feature-rich, modern and fully cross-platform password manager refer to the features list and FAQ for more detail. The Electronic Frontier Foundation mention KeePassXC as "an example of a password manager that is open-source and free." The tech collective PrivacyTools has included KeePassXC in their list of recommended password manager software because of its active development. It started as a community fork of KeePassX (itself a cross-platform fork of KeePass ). This entry was posted in Privat and tagged HowTo, Linux on 1 by Sebastian Spaeth.a free and open-source password manager. It might be useful on the wiki if confirmed by other users of the portable version on windows…. I realize that this is not the fault of keepassxc, but given the multitude of reported errors and the unhelpful error message I think this might be of use for other users of the Portable Version. I autostart BINARY2 now on system start (Hit WIN-R, type shell:startup and paste a “link” to the correct keepassxc.exe) and that seems to do the trick for me. (not sure what weird wrapper the first binary is). Somehow, in this case the proxy will probably try to talk to the wrong binary. If I start the former, I will get a key exchange failed error. IF I directly start the latter binary, the Firefox extension is able to connect to the running keepassxc. The binary in the former directory is what is started when one starts keepassxc through the PortableApps menu. The latter is also the directory which contains the keepassxc-proxy.exe. I noted that there are actually 2 binaries:Ĭ:\Users\spaetz\bin\PortableApps\KeePassXCPortable\KeePassXCPortable.exe (248kb) andĬ:\Users\spaetz\bin\PortableApps\KeePassXCPortable\App\KeePassXC\KeePassXC.exe (7094kb) NO combination of options, deleting of keepassxc and/or the browser extension, deletion of registry entries, or using a fresh Firefox profile helped. When I turned off the use of a proxy in the keepassxc settings (Browser integration -> Advanced), starting Firefox actually also started a keepassxc instance automatically, however all I still got was a “key exchange failed” error. Turning on add-on debugging led to the same result and not more helpful information. However, trying to connect, all I got is a “key exchange failed” error. When I started Firefox, I got a running keepassxc-proxy.exe process as a Firefox child process. which pointed to a correct path “C:\Users\spaetz\bin\PortableApps\KeePassXCPortable\App\KeePassXC\keepassxc-proxy.exe”.it pointed to the correct _browser_firefox.json file.I had a registry key under “Computer\HKEY_CURRENT_USER\Software\Mozilla\NativeMessagingHosts\_browser”,.Initial Problem PortableApps Keepassxc (2.5.3) It was quickly closed there as the devs don’t want to support PortableApps versions, fair enough, but would perhaps saved them a few support requests if the information were to be find in their development wiki): See below what I did, in the hope that it might be useful for others and for future reference to myself (I posted this in the portable app forum too -and- as the problem seems widespread as an issue in the keepassxc issue tracker. After lots of trial and error and debugging attempts (debugging led to no more detail than “key exchange failed”, unfortunately), I have gotten it working. However, I – seemingly like many others – have trouble to connect the portable version with the Firefox browser extension to enable autofill. The keepassxc devs offer a portable zip for download (KUDOS!) but I do like the seamless upgrades and the start menu the PortableApps platform offers. On my Windows work laptop I am using the PortableApps version. I am using the excellent KeepassXC on all my computers, it works on Windows (work-supplied laptop), Linux (home) and there are mobile clients too. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |