| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
tor-netdir: Add spec link to flag descriptions
See merge request tpo/core/arti!3768
|
| | | |
|
| | |
| |
| |
| | |
No need to over-engineer this, let's keep it simple.
|
| |/
|
|
|
|
|
|
|
|
|
| |
This commit adds a method called `is_flagged_exit` to `RelayDetails` in
order to check whether the node is considered to be usable as an exit or
not.
In the Tor VPN app, we need this feature for generating a list of exit
relays (per country). Right now, we do this in an incorrect way by only
checking on whether port 443 is in the exit policy, which is not a
sufficient criteria.
|
| |
|
|
| |
Now we only need one type.
|
| |
|
|
|
|
| |
Since we don't know what kind of traffic we'll use a rendezvous
point for, we don't want to use it if it isn't "Fast" (reasonably
high bw) and "Stable" (unlikely to crash soon).
|
| |
|
|
|
|
| |
> The actual impact of this patch is to prevent usage of MiddleOnly
> relays as Introduction Points. The Rendezvous Point logic isn't
> hooked up yet - nick
|
| | |
|
| |
|
|
|
|
|
| |
This implements the client side of proposal 321.
It's a breaking change in netdir, since in_same_family now takes an
extra argument.
|
| | |
|
| |
|
|
| |
This was an open-coded specialisation. Remove the one call site.
|
| | |
|
| | |
|
| |
|
|
|
| |
Everybody outside of tor-netdir should use
HasRelayIds::same_relay_ids, whose intent is clearer.
|
| |
|
|
| |
These were only used for testing.
|
| |
|
|
|
|
|
|
| |
In *RelayDetails, this is just a matter of changing a bunch of
`self`s to `self.0`.
Additionally, I've added temporary stub functions to delegate to the
new functions.
|
| |
|
|
| |
This is 99% code movement.
|
|
|
I'm going to use this wrapper type to hide checks
that should mostly not be used without careful thinking.
There are also comments here explaining when you'd want to use these
types, and when you shouldn't.
Part of #504.
|
