[tor-relays] rdsys was ignoring BridgeDistribution

[meskio]

As mentioned before[0] BridgeDB now uses rdsys as backend. I just found out that 
there was a bug in rdsys and the BridgeDistribution configuration was ignored.

Private bridges configured with 'BridgeDistribution none' might have being 
distributed by bridgedb if they were not configured with 
'PublishServerDescriptor 0'. Disabling PublishServerDescriptor stops the bridge 
from sending it's descriptor to the bridge authority, so rdsys doesn't know it 
exists.

Other bridges configured to be used by an specific distributor might have being 
distributed by a different one.

This has being happening from February 28th ~12:00UTC until today March 4 
~12:00UTC.

You can search for your hashed fingerprint in the pool assignments during this 
period if you want to know to what distributor was your bridge assigned to:
  https://metrics.torproject.org/collector/recent/bridge-pool-assignments/
Only bridges assigned to moat, email or https might have being distributed, as 
telegram, settings and reserved bridges are not distributed at the moment.

The metrics relay search[1] will take some time to display the new assignments.
I'm sorry for the situation.


[0] https://lists.torproject.org/pipermail/tor-relays/2022-February/020365.html
[1] https://metrics.torproject.org/rs.html

-- 
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20220304/3d76545a/attachment.sig>