Opened 2 years ago

Last modified 3 weeks ago

#23362 new enhancement

consider performing network operations in a dedicated process

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-security, tbb-sandboxing, ff78-esr
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor44-can

Description

ESR59 will have approx. 8 processes, excluding content processes. And it makes sense to run them all in strong sandboxes without network access. To achieve this it could be helpful to discuss and coordinate this work with Mozilla in https://bugzilla.mozilla.org/show_bug.cgi?id=1322426.

Child Tickets

Change History (11)

comment:1 Changed 2 years ago by cypherpunks

It would be very useful if this networking process executed a file separate from torbrowser or plugin-processes, since then it could be given a separate domain/subject in MAC policy. The same goes for any process with different required privileges.

I know nothing about Mozilla's planned design other than this ticket and the referenced bug. Perhaps someone with Mozilla's ear could make a case for this?

comment:2 Changed 2 years ago by tom

I haven't heard anything about that bug, so I suspect it is a future wishlist item but not actively being planned out.

comment:3 Changed 21 months ago by gk

Keywords: ff60-esr added; ff59-esr removed

Firefox 60 is the new ESR.

comment:4 Changed 21 months ago by cypherpunks

Summary: consider performing network operations in a dedicated process for ESR59consider performing network operations in a dedicated process for ESR60

comment:5 Changed 16 months ago by gk

Keywords: ff67-esr added; ff60-esr removed

Might be something for esr67.

comment:6 Changed 16 months ago by cypherpunks

Keywords: tbb-sandboxing added
Summary: consider performing network operations in a dedicated process for ESR60consider performing network operations in a dedicated process

According to BMO, this decision has been taken, and the current progress is tracked here:
https://wiki.mozilla.org/Necko:_Sandboxing_TCP/UDP_socket_in_a_separate_process
(so this ticket can be closed)

comment:7 in reply to:  6 Changed 16 months ago by gk

Replying to cypherpunks:

According to BMO, this decision has been taken, and the current progress is tracked here:
https://wiki.mozilla.org/Necko:_Sandboxing_TCP/UDP_socket_in_a_separate_process
(so this ticket can be closed)

Let's keep it open for a bit. Although the changes might be too pervasive to backport there might still be things we could test in an alpha.

comment:8 Changed 16 months ago by arthuredelstein

Keywords: ff68-esr added; ff67-esr removed

Version 68 of Firefox will be the next ESR.

comment:9 Changed 3 months ago by pili

Sponsor: Sponsor44-can

Adding Sponsor 44 to ESR68 tickets

comment:10 Changed 3 weeks ago by gk

Keywords: ff76-esr added; ff68-esr removed

Did not get ready for ESR68.

comment:11 Changed 3 weeks ago by gk

Keywords: ff78-esr added; ff76-esr removed

There is no 76 ESR.

Note: See TracTickets for help on using tickets.