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

TBB detection not working in SI for TBB 10.0.4 on MacOS #5626

Closed
zenmonkeykstop opened this issue Nov 13, 2020 · 2 comments · Fixed by #5647
Closed

TBB detection not working in SI for TBB 10.0.4 on MacOS #5626

zenmonkeykstop opened this issue Nov 13, 2020 · 2 comments · Fixed by #5647

Comments

@zenmonkeykstop
Copy link
Contributor

Description

TBB 10.0.4 on MacOS is incorrectly identified as a non-Tor browser in the Source Interface

Steps to Reproduce

Start TBB 10.0.4 and visit an SI address.

Expected Behavior

  • message displayed indicating that user should change security setting

Actual Behavior

  • message displayed encouraging user to use Tor Browser "instead"

Untitled 2

Comments

(Detection also failing on securedrop.org.)

@harrislapiroff
Copy link
Contributor

I'll take a look at this for SDO purposes and share the necessary updates here

@harrislapiroff
Copy link
Contributor

Looks like the issue is the bit of the user agent string to match the macOS version. The current string:

const TBB_UA_REGEX = /Mozilla\/5\.0 \((Windows NT 10\.0|X11; Linux x86_64|Macintosh; Intel Mac OS X 10\.14|Windows NT 10\.0; Win64; x64); rv:[0-9]{2}\.0\) Gecko\/20100101 Firefox\/([0-9]{2})\.0/;

An updated string that works:

const TBB_UA_REGEX = /Mozilla\/5\.0 \((Windows NT 10\.0|X11; Linux x86_64|Macintosh; Intel Mac OS X 10\.[0-9]{2}|Windows NT 10\.0; Win64; x64|Android; Mobile); rv:[0-9]{2}\.0\) Gecko\/20100101 Firefox\/([0-9]{2})\.0/

(Note the specific bit that I changed was: Intel Mac OS X 10\.14} => Intel Mac OS X 10\.[0-9]{2}

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

Successfully merging a pull request may close this issue.

2 participants