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

Expose Tor log in brave://tor #8106

Closed
fmarier opened this issue Feb 6, 2020 · 6 comments
Closed

Expose Tor log in brave://tor #8106

fmarier opened this issue Feb 6, 2020 · 6 comments

Comments

@fmarier
Copy link
Member

fmarier commented Feb 6, 2020

Description

A friend of mine told me that he's found our Tor support quite unreliable on his Linux desktop (it's possible he's running into #8076 or #8129 at the moment).

What he suggested is that we expose the tor daemon log somewhere so that tech-savvy users can more easily figure out what's wrong (and send us useful bug reports).

Orbot on Android does this in a nice way, but perhaps all we need for an MVP would be to redirect the daemon log file to an in-memory structure and make it viewable from an internal URL like brave://tor.

Designs

The Tor connection status is displayed prominently on the NTP with a flashing indicator to draw attention and show progress. This would give some hint that the reason why NTP is not connecting to a webpage that a user entered is because it's waiting for this Tor connection to complete. For users who are so inclined to dig into the details, View logs links to brave://tor.

The new, simplified NTP design ensures that no scrolling would occur for all but the very smallest screens - the content height is not much longer than an extension panel.

connection

User flow

image

Search bar

The search bar has DDG set as the default. The user can click on the search bar dropdown to select a different SE for a particular search query.
image

Keyboarding

image
image

Assets

Figma: https://www.figma.com/file/5THkuEtO2Ewn9LfqrHZP9a/Desktop-Private-and-TOR-Windows?node-id=102%3A2574

@fmarier
Copy link
Member Author

fmarier commented Feb 28, 2020

@doegox Next time you encounter this problem, can you email me your ~/.config/BraveSoftware/Brave-Browser/tor/data/tor.log?

That is BTW the location of the log file you were after :)

@doegox
Copy link

doegox commented Feb 29, 2020

Oh thanks! Will do

@doegox
Copy link

doegox commented Aug 6, 2020

@doegox Next time you encounter this problem, can you email me your ~/.config/BraveSoftware/Brave-Browser/tor/data/tor.log?

The issue still occurs.
When it occurs, there is nothing in the logs at all, as if the tor module didn't start at all.
Restarting Brave (sometimes several times) fixes the issue.

@fmarier
Copy link
Member Author

fmarier commented Aug 6, 2020

@doegox I have also seen this on my machine but only the first time I opened a Tor window. In other words, what I saw was this:

  1. Open a Tor window (doesn't work).
  2. Close the Tor window.
  3. Open a Tor window (this one works).

In your case, it also doesn't work the second time and you need to exit Brave and start it again?

Is there anything relevant in stdout/stderr? Syslog? dmesg?

@karenkliu
Copy link

Designs added!

@fmarier
Copy link
Member Author

fmarier commented May 21, 2021

Now available at brave://tor-internals/.

@fmarier fmarier closed this as completed May 21, 2021
@fmarier fmarier added this to the 1.21.x - Release milestone May 21, 2021
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

3 participants