Opened 5 years ago

Closed 5 years ago

#16334 closed task (fixed)

Make sure websockets in workers don't leak DNS requests

Reported by: gk Owned by: mikeperry
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Keywords: ff38-esr, tbb-linkability, tbb-5.0a3-essential, TorBrowserTeam201506, MikePerry201506
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

WebSockets are available in WebWorkers now (https://bugzilla.mozilla.org/show_bug.cgi?id=504553). We need to double-check against fresh DNS leaks.

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by mikeperry

Keywords: tbb-5.0a3-essential added

Tag the set of things we should aim to understand/fix for the fist FF38-based TBB (5.0a3, on June 30th).

comment:2 Changed 5 years ago by mikeperry

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

comment:3 Changed 5 years ago by mikeperry

Keywords: TorBrowserTeam201506 MikePerry201506 added

comment:4 Changed 5 years ago by mikeperry

Resolution: fixed
Status: assignedclosed

This did not turn up in my networking review as a new source of DNS or networking calls, and I looked at the specific patches and it appears that most of the work was to refactor the existing websocket code in way that it can be used from either worker threads or the main thread. I think this is fine.

Note: See TracTickets for help on using tickets.