When CircuitPadding is implemented in Tor, set it to 0 in sbws

In #28693 (moved), we will implement a tor option for circuit padding. When that option is implemented, we should set it to 0 in sbws.

changed milestone to %sbws: 1.1.x-final

added changes-version-patch component::core tor/sbws milestone::sbws: 1.1.x-final padding parent::29954 priority::medium sbws-11x-final-removed-20190312 scanner severity::normal sponsor::2 status::new tor-cell tor-relay type::enhancement wtf-pad labels

Unparenting this ticket

Trac:
Parent: #28693 (moved) to N/A

sbws doesn't want padding on its circuits, because padding interferes with bandwidth measurements

Trac:
Parent: N/A to #28693 (moved)

Take some wtf-pad stuff out of 041-proposed

Moving to 1.1 milestone since CircuitPadding is not implemented yet

Trac:
Milestone: sbws: 1.0.x-final to sbws: 1.1.x-final

Add keyword to tickets that imply a change of version patch, since it might affect the results, but in a backwards compatible way and doesn't add functionality.

Trac:
Keywords: N/A deleted, changes-version-patch added

Move tickets that can wait to next month

Trac:
Keywords: N/A deleted, sbws-11x-final-removed-20190312 added

Actually remove them from milestone

Trac:
Milestone: sbws: 1.1.x-final to sbws: unspecified

Trac:
Keywords: N/A deleted, scanner added
Parent: #28693 (moved) to #29954 (moved)

Move all WTF-PAD tickets that do not have a sponsor into sponsor2.

Trac:
Sponsor: N/A to Sponsor2

Trac:
Keywords: N/A deleted, 041-must added

Bugfix on 1.1.

Trac:
Milestone: sbws: unspecified to sbws: 1.1.x-final

The CircuitPadding torrc option has been merged to master, FYI (#28693 (moved)). This can be implemented once swbs start using 0.4.1.

The actual padding machines we're implementing (#28634 (moved)) only pad HS circuits, though, which sbws does not use. So this is not essential yet, even when 0.4.1 is stable.

Replying to mikeperry:

The CircuitPadding torrc option has been merged to master, FYI (#28693 (moved)). This can be implemented once swbs start using 0.4.1.

sbws uses the installed Tor version. So we should add the CircuitPadding option to sbws. But put it in the list of options that might fail at runtime.

The actual padding machines we're implementing (#28634 (moved)) only pad HS circuits, though, which sbws does not use. So this is not essential yet, even when 0.4.1 is stable.

Thanks, that's useful for us to know.

We won't block on this ticket, because padding doesn't affect sbws circuits yet. But we should keep the sbws options up to date with tor, because that's an sbws best practice.

Trac:
Keywords: 041-must deleted, 041-should added

Trac:
Keywords: 041-should deleted, N/A added

mentioned in issue #28737 (moved)

mentioned in issue #29954 (moved)

moved to tpo/network-health/sbws#28694 (closed)

mentioned in issue tpo/network-health/sbws#28737 (closed)