They were used to resolve the IP of the destination and check
whether an exit policy allows to exit to that IP, but when the
destination is a CDN, the IP locally resolved would be different
to the IP resolved in the exit, and when the IP resolved to
IPv6, it was possible that the scanner didn't have IPv6.
The correct method to check whether an exit policy allows to exit
to an IP, would be to resolve the domain via Tor itself using
RESOLVE and ADDRMAP events with that exit.

When parsing results support old ones without new bandwidth
attributes, as descriptor bandwidth burst, consensus_bandwidth
and consensus bandwidth is unmeasured.

attributes to BWLine. Add methods to obtain them from results.

In order to use it in torflow's scaling method.
Tech-debt is growing repeating Relay in relaylist and resultdump,
Relay should have Results, not Result has Relay

Closes #28645. Bugfix v0.2.0.

To test that torflow's scaling is using the minimum of all the
descriptor bandwidth values.

from sbws scaling to torflow's scaling, where the descriptor
bandwidth is calculated from the minimum of all the descriptor
bandwidth values.
And use the bandwidth-file-spec.txt text instead.

v3bwfile: replace desc_bw_obs by desc_bw

Torflow's scaling takes the minimum of all the descriptor
bandwidth values, not only the descriptor observed bandwidth.

And method to obtain it from results.

This way it can be obtained in a different way (for instance, the
mean, not the last) and it also avoids not obtaining any value in
case the last is None.

In order to use it in torflow's scaling method.

In order to use it in torflow's scaling method

The flags are: not having a badflag and the policy allows to exit
to a port.

The flags are: not have the badflag and the policy allows to exit
to a port.

The flags are: not having a badexit and the policy allows to exit
to a port.

In order to do not relay on resolving a domain locally to check
the IP in the exit policy.

Instead create a changelog before new releases.

Closes ticket #28572.

sbws should exclude results, then check for the minimum number of results.

Closes bug 28572.

Even if that method is call from generate with torflow's scaling
by default.

So that is less confusing that it's the default.
We already have an option for linear scaling and no scaling.

Continue running with defaults when the config argument is provided
but not found. This could be the case of system packages.

sbws is getting a significant number of build failures due to keyserver failures.

Using the high-availability keyserver pool reduces the probability of failure.