From #18329 (moved), we added a new bridge-server-descriptor line: bridge-distribution-request, which, if set to "none" should tell BridgeDB not to distribute a bridge. This allows, for example, BridgeDB to avoid distributing the default Tor Browser bridges, and allows other bridges to not be distributed, but to still submit their usage statistics for Metrics.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Is it live? Could you please provide a descriptor with examples of this (both the none and the non-none values)? I'd also like the field to be documented before we add it to Stem.
Hi atagar! There's a spec patch from #18329 (moved) which should be usable to implement this. It's not live in Tor yet, since #18329 (moved) is waiting (among other things) for it to be parseable by BridgeDB (and hence Stem), before merging it since it would be bad if operators thought their bridge was private and it wasn't actually respected.
Trac: Status: closed to reopened Resolution: user disappeared toN/A
Ha! So spec patch is awaiting tor which is awaiting bridgedb which is awaiting stem which is awaiting the spec. Thanks, you made me chuckle this morning. :P
No big rush but this will need to be followed up with the tor spec change otherwise I'll revert this in a future revision (I have a 'must be in the spec' policy because Stem's predecessor, TorCtl, accumulated support for fields that never existed which was confusing). Happy to make an exception here, just giving a head's up that this will need to be followed up with the addition on tor's side.