#20940 closed task (fixed)

Deprecate x86 support.

Reported by: yawning Owned by: yawning
Priority: High Milestone:
Component: Archived/Tor Browser Sandbox Version:
Severity: Normal Keywords: sandbox-security Yawning201612
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

There's lots of reasons why this is a good idea:

  • Weaker ASLR.
  • Seccomp related headaches.
    • I wanted to use gosecco to do runtime seccomp rule generation, but it only supports amd64.
    • libseccomp2 shipped on Debian stable generates wrong code on amd64, so the current workaround of pre-generating compiled bpf at build time using libseccomp2 from backports precludes runtime code generation, degrading sandbox effectiveness across all platforms.
    • x86 systems can't effectively filter out arguments to a lot of socket related system calls because of socketcall().
  • Supporting hardware I don't have, running software I don't use, to ultimately obtain results that are empirically worse than the other supported platform is a poor use of development time.
  • Tails gave up on supporting 32 bit userland (https://labs.riseup.net/code/issues/8183).

Child Tickets

TicketStatusOwnerSummaryComponent
#21254closedyawningDeprecate x86 and arm support.Archived/Tor Browser Sandbox

Change History (9)

comment:1 Changed 18 months ago by cypherpunks

For as much as an anonymous shared account's opinion is worth, I support this consideration. Not only is x86_32 weaker in many ways compared to x86_64 as you pointed out, but the processors that are still that old have ancient errata which screw with pretty much any sandboxing you'd attempt (cache-based privesc, issues with synchronizing NX state across cores, etc). I don't think it's fair to the majority for your time to be sucked up supporting people who won't be protected well anyway.

Perhaps in the future, when there are more active contributors to this project and it's more mature, supporting x86_32 would be more practical. But for now, it'd just be a time waster, IMO.

comment:2 Changed 18 months ago by yawning

Keywords: sandbox-security added

comment:3 Changed 18 months ago by yawning

Keywords: Yawning201612 added
Status: newaccepted

I'm going to do this before tagging 0.0.3.

comment:4 Changed 18 months ago by yawning

Priority: MediumHigh

comment:5 Changed 18 months ago by yawning

Summary: Consider deprecating x86 support.Deprecating x86 support.

Rename the ticket, because it will happen.

Branch: https://git.schwanenlied.me/yawning/sandboxed-tor-browser/src/bug20940

Merge pending testing.

comment:6 Changed 18 months ago by yawning

Summary: Deprecating x86 support.Deprecate x86 support.

comment:8 Changed 17 months ago by cypherpunks

Resolution: fixed
Status: closedreopened

comment:9 Changed 17 months ago by yawning

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.