You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of right now keepassxc assumes that the install is done either by the native package manager, or Flatpak and nothing else.
When the install is done by the tor browser itself (or the launcher, they are equal here) the integration with the extension does not work.
Cause & possible fix
That is because there is no check to determine if the install has been done by the Tor thing.
I do not know what would be a good way to do it.
Maybe check if ~/.local/share/torbrowser/tbb/x86_64/tor-browser/Browser/TorBrowser/Data/Browser/profiles.ini exists and adjusting the tor path prefix like in line 222:
if (browser == SupportedBrowsers::TOR_BROWSER) {
basePath = QDir::homePath() + "/.local/share";
Steps to Reproduce
Install Tor browser
as a native package and wait for the update
from the torbrowser-launcher
Install the keepassxc extension in the browser
Turn on the integration in KeePassXC
Expected Behavior
The browser plugin works.
Actual Behavior
KeePassXC puts the native.messaging.hosts
Context
Distros update their TorBrowser slower than the Tor Project itself
some even prefer users to use the torbrowser-launcher bundle
Tor Browser autoupdates
KeePassXC - 2.7.6
Operating System: Linux
The text was updated successfully, but these errors were encountered:
Overview
As of right now keepassxc assumes that the install is done either by the native package manager, or Flatpak and nothing else.
When the install is done by the tor browser itself (or the launcher, they are equal here) the integration with the extension does not work.
Cause & possible fix
That is because there is no check to determine if the install has been done by the Tor thing.
I do not know what would be a good way to do it.
Maybe check if
~/.local/share/torbrowser/tbb/x86_64/tor-browser/Browser/TorBrowser/Data/Browser/profiles.ini
exists and adjusting the tor path prefix like in line 222:Steps to Reproduce
Expected Behavior
The browser plugin works.
Actual Behavior
KeePassXC puts the native.messaging.hosts
Context
torbrowser-launcher
bundleKeePassXC - 2.7.6
Operating System: Linux
The text was updated successfully, but these errors were encountered: