Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with Tor Browser integration on Linux #10438

Open
o0nd7ots opened this issue Mar 15, 2024 · 0 comments
Open

Problems with Tor Browser integration on Linux #10438

o0nd7ots opened this issue Mar 15, 2024 · 0 comments

Comments

@o0nd7ots
Copy link

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:

    if (browser == SupportedBrowsers::TOR_BROWSER) {
        basePath = QDir::homePath() + "/.local/share";

Steps to Reproduce

  1. Install Tor browser
  • as a native package and wait for the update
  • from the torbrowser-launcher
  1. Install the keepassxc extension in the browser
  2. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants