Reduce binary size for client-only tor

Uncompressed, the Tor executable and associated libs as bundled in Tor Browser is 7.7 MB. If we want other browsers to adopt Tor, it would be good to make it a lot smaller if possible. What is responsible for the bulk? Can we cut out unused code from libcrypto and other libraries? Or can we reuse some shared libraries from the browser? Would it help to chop out unused code that implements relays, hidden services, etc.?

changed milestone to %Tor: unspecified in legacy/trac

added 034-removed-20180328 in Legacy / Trac 034-triage-20180328 in Legacy / Trac 035-roadmap-subticket in Legacy / Trac 035-triaged-in-20180711 in Legacy / Trac component::core tor/tor in Legacy / Trac ex-sponsor-19 in Legacy / Trac ex-sponsor19 in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac type::task in Legacy / Trac labels

Trac:
Milestone: N/A to Tor: 0.3.2.x-final

Trac:
Summary: can we make a thin Tor proxy? to Reduce binary size for client-only tor

Trac:
Description: Uncompressed, the Tor executable and associated libs as bundled in Tor Browser is 7.7 MB. If we want other browser to adopt Tor, it would be good to make it a lot smaller if possible. What is responsible for the bulk? Can we cut out unused code from libcrypto and other libraries? Or can we reuse some shared libraries from the browser? Would it help to we chop out unused code that implements relays, hidden services, etc.?

to

Uncompressed, the Tor executable and associated libs as bundled in Tor Browser is 7.7 MB. If we want other browsers to adopt Tor, it would be good to make it a lot smaller if possible. What is responsible for the bulk? Can we cut out unused code from libcrypto and other libraries? Or can we reuse some shared libraries from the browser? Would it help to chop out unused code that implements relays, hidden services, etc.?

Trac:
Sponsor: N/A to Sponsor8-can

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final

Deferring various "new"-status enhancement tickets to 0.3.4

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: 0.3.5.x-final

Trac:
Parent: N/A to legacy/trac#26630 (moved)
Keywords: 034-removed-20180328 deleted, 034-removed-20180328 035-roadmap-subticket added

What is the actionable work for this ticket? Should subtasks be created (or existing subtasks linked here)?

For example, legacy/trac#26631 (moved) could be a good candidate subtask, or subtasts created from a recent modularization session: https://trac.torproject.org/projects/tor/wiki/org/meetings/2018Rome/Notes/TorModularization.

Should there be some description here about what a sufficient reduction in size would be?

Subtasks would be good -- any significant improvement would be valuable. We haven't committed to a specific size, so IMO we should begin by looking to see where the binary size is actually going, and see whether there are low-hanging fruit.

Trac:
Keywords: 034-removed-20180328 035-roadmap-subticket deleted, 034-removed-20180328, 035-triaged-in-20180711, 035-roadmap-subticket added

We've done a fair bit of this; any more can come in 0.3.6

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: 0.3.6.x-final

Trac:
Sponsor: Sponsor8-can to Sponsor19

Tor 0.3.6.x has been renamed to 0.4.0.x.

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final

I think this is a great ticket to work on, but it is not in the critical path to getting the anti-censorship team back up and going, so I'm going to remove the Sponsor19 tag.

This change doesn't mean we should not do this ticket -- just that we should decide on its priority compared to all the other tickets we also think we should do to make Tor better.

Trac:
Sponsor: Sponsor19 to Sponsor8

Trac:
Sponsor: Sponsor8 to N/A

Trac:
Milestone: Tor: 0.4.0.x-final to Tor: unspecified
Sponsor: N/A to SponsorM-can

Trac:
Sponsor: SponsorM-can to Sponsor19-can

Trac:
Parent: legacy/trac#26630 (moved) to N/A

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

Trac:
Keywords: N/A deleted, ex-sponsor-19 added

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

Trac:
Sponsor: Sponsor19-can to N/A
Keywords: N/A deleted, ex-sponsor19 added

mentioned in issue legacy/trac#25610 (moved)

mentioned in issue legacy/trac#26630 (moved)

mentioned in issue legacy/trac#26631 (moved)

moved from legacy/trac#21814 (moved)

added Task label and removed 1 deleted label

removed 1 deleted label

This is a parent-ticket, and gitlab doesn't do those very well.

closed

marked this issue as related to arti#87