On Mac OS X 10.11.6 , attempting to open a local HTML file using the "Open with" -> TorBrowser.app context menu option results in the file being opened in the default browser instead of TorBrowser. A new TorBrowser window is initialized but the file isn't opened in TorBrowser.
Trac: Username: hdub
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Trac: Summary: Selecting Open With TorBrowser in Mac OS X Finder Opens File in Default Browser Instead to Selecting Open With TorBrowser on a Mac Opens the File in Default Browser Instead Owner: tbb-team to brade Component: Applications/Tor Browser to Applications/Tor Launcher
This is a Tor Browser bug, and a Tor Launcher bug.
And the exact behaviour also depends on:
if Firefox is installed or not,
if installed, which of Tor Browser or Firefox is registered under the Firefox 'Bundle creator OS Type code' MOZB (#17670 (moved)),
if Tor Browser is already open or not (that is, whether Tor Launcher or Tor Browser handles the open document request), and
if Tor Browser or Firefox or some other browser is the default system browser.
We can focus on the Tor Launcher bug in this ticket: Tor Launcher should handle the Open Document request, and pass it on to Tor Browser once it finishes launching. If it doesn't handle the Open, macOS will try to open it in the default browser instead.
This is a Tor Browser bug, and a Tor Launcher bug.
And the exact behaviour also depends on:
if Firefox is installed or not,
if installed, which of Tor Browser or Firefox is registered under the Firefox 'Bundle creator OS Type code' MOZB (#17670 (moved)),
if Tor Browser is already open or not (that is, whether Tor Launcher or Tor Browser handles the open document request), and
if Tor Browser or Firefox or some other browser is the default system browser.
We can focus on the Tor Launcher bug in this ticket: Tor Launcher should handle the Open Document request, and pass it on to Tor Browser once it finishes launching. If it doesn't handle the Open, macOS will try to open it in the default browser instead.
This issue is not just with Firefox as the default browser. Try it with Chrome as the default browser; it will open a Tor Browser instance if there isn't already one running, but the file is opened in Chrome.
This is a Tor Browser bug, and a Tor Launcher bug.
And the exact behaviour also depends on:
if Firefox is installed or not,
if installed, which of Tor Browser or Firefox is registered under the Firefox 'Bundle creator OS Type code' MOZB (#17670 (moved)),
if Tor Browser is already open or not (that is, whether Tor Launcher or Tor Browser handles the open document request), and
if Tor Browser or Firefox or some other browser is the default system browser.
We can focus on the Tor Launcher bug in this ticket: Tor Launcher should handle the Open Document request, and pass it on to Tor Browser once it finishes launching. If it doesn't handle the Open, macOS will try to open it in the default browser instead.
This issue is not just with Firefox as the default browser. Try it with Chrome as the default browser; it will open a Tor Browser instance if there isn't already one running, but the file is opened in Chrome.
Yes, as I said, this issue happens when the default browser is some other browser than Firefox or Tor Browser.
But the exact behaviour depends on whether Firefox is installed, because macOS confuses Firefox with Tor Browser in some circumstances.
This behaviour appears to be fixed in 7.0.1 on macOS 10.12.5, but it now also opens a second TorBrowser window when you open a local file in TorBrowser.
This behaviour appears to be fixed in 7.0.1 on macOS 10.12.5, but it now also opens a second TorBrowser window when you open a local file in TorBrowser.
What is happening in this case is that the first window (the one that contains the "Open With" file) is opened before Tor Launcher has finished setting up the Tor network connection. Tor Launcher tries to block startup of the browser until bootstrapping completes, but another part of the browser handles the open request anyway.
The right fix is probably to do what teor said at the end of comment:2. Unfortunately, it may be a lot of work to modify the Firefox code that Tor Browser is based on to queue open file requests rather than processing them right away.
This behaviour appears to be fixed in 7.0.1 on macOS 10.12.5, but it now also opens a second TorBrowser window when you open a local file in TorBrowser.
What is happening in this case is that the first window (the one that contains the "Open With" file) is opened before Tor Launcher has finished setting up the Tor network connection. Tor Launcher tries to block startup of the browser until bootstrapping completes, but another part of the browser handles the open request anyway.
The right fix is probably to do what teor said at the end of comment:2. Unfortunately, it may be a lot of work to modify the Firefox code that Tor Browser is based on to queue open file requests rather than processing them right away.
I think an extra window is something we can live with: it's not a security issue any more, because opening links and documents with Tor Browser as the default browser works in 7.0.1.
I think an extra window is something we can live with: it's not a security issue any more, because opening links and documents with Tor Browser as the default browser works in 7.0.1.
Do you want to close this ticket, mcs?
Yes, and done.
Trac: Resolution: N/Ato fixed Status: new to closed