Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#26874 closed defect (fixed)

Investigate UNC path restrictions failure in Tor Browser 8.0a9

Reported by: gk Owned by: pospeselr
Priority: Very High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: ff60-esr, tbb-proxy-bypass, TorBrowserTeam201808R
Cc: tbb-team Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Filippo Cavallarin reported that the UNC path restrictions that got made available through are not working in Tor Browser 8.0a9. Surprisingly, Tor Browser 7.5.6 and Firefox 60.1.0 ESR are fine.

Child Tickets

Change History (5)

comment:1 Changed 2 years ago by pospeselr

Owner: changed from tbb-team to pospeselr
Status: newassigned

comment:2 Changed 2 years ago by boklm

Cc: tbb-team added

comment:3 Changed 2 years ago by gk

Keywords: TorBrowserTeam201808 added; TorBrowserTeam201807 removed

Move our tickets to August.

comment:4 Changed 2 years ago by pospeselr

Keywords: TorBrowserTeam201808R added; TorBrowserTeam201808 removed
Status: assignedneeds_review

Fix for #26874.

This issue also exists in ESR60 and any fix will need to be uplifted.

comment:5 Changed 2 years ago by gk

Resolution: fixed
Status: needs_reviewclosed

I reverted the slightly different patch we got from Valentin Gosu for 60.1.0esr (that's done in commit bd4abf8ba8f4e1aea2acd4b895274f646ed951a8) and cherry-picked the one that actually shipped in 60.1.0esr on top of it (done in commit bd4abf8ba8f4e1aea2acd4b895274f646ed951a8). Then I cherry-picked the fix for this issue which Mozilla pushed to its esr60 repo (commit dae353ff5f2d033b9b87ebf2a5f833c87068d4a3). Everything is on tor-browser-60.1.0esr-8.0-1.

Thus, we should be good here now, thanks everyone.

Version 0, edited 2 years ago by gk (next)
Note: See TracTickets for help on using tickets.