 Roger Dingledine
|
0c40dda3ad
explain an argument in a function comment
|
14 years ago |
 Nick Mathewson
|
748350ace1
Instead of checking whether we have unremoved intro points, check for usable ones
|
14 years ago |
|
Roger Dingledine
|
b8b557dcb2
better user-facing warnings for unexpected last hops
|
14 years ago |
|
Roger Dingledine
|
f7a5bc16d6
warn if we launch too many circuits for a given stream
|
14 years ago |
|
Roger Dingledine
|
f962dda8c1
revert most of ef81649d2fc
|
14 years ago |
|
Nick Mathewson
|
8ee92f28e0
Add a circuit_purpose_to_string() function, and use it
|
14 years ago |
 Sebastian Hahn
|
e03e90bf59
Fix a check-spaces complaint
|
14 years ago |
|
Sebastian Hahn
|
92ec36a061
Explain the "using anyway" log message better
|
14 years ago |
|
Sebastian Hahn
|
8e2904e269
Fix a log msg
|
14 years ago |
|
Nick Mathewson
|
79a3b3cd37
Check transition of circuit purpose from INTRO->GENERAL if nodes are constrained
|
14 years ago |
|
Nick Mathewson
|
6afad6b691
When cannibalizing a circuit, make sure it has no ExcludeNodes on it
|
14 years ago |
|
Nick Mathewson
|
80adb3de50
When there is a transition in permitted nodes, apply it to trackexithosts map
|
14 years ago |
|
Nick Mathewson
|
128582cc1f
Simplify calls to routerset_equal
|
14 years ago |
|
Nick Mathewson
|
84f0e87c6a
If we have chosen an exit that shares a family with all bridges, fail the circuit
|
14 years ago |
|
Nick Mathewson
|
b59a289365
Do not try to download descriptors for bridges in ExcludeNodes.
|
14 years ago |
|
Nick Mathewson
|
ad78bafb71
Correct the behavior of .exit with ExcludeNodes, StrictNodes, etc.
|
14 years ago |
|
Nick Mathewson
|
ed7c267743
Note another place that we need to fix a 1090 issue.
|
14 years ago |
|
Nick Mathewson
|
4851de554d
Do not automatically ignore Fast/Stable for exits when ExitNodes is set
|
14 years ago |
|
Nick Mathewson
|
e4689d8402
Note a slightly less likely way to violate ExcludeNodes
|
14 years ago |
|
Nick Mathewson
|
db2fd28308
Note that circuit purpose changing can violate ExcludeNodes
|
14 years ago |
|
Nick Mathewson
|
ca74badbe9
If we're excluded, and StrictNodes is set, do not do self-tests.
|
14 years ago |
|
Nick Mathewson
|
affdec8d04
Add an XXX022-1090 to note consider_exit_fmily b0rkenness
|
14 years ago |
|
Roger Dingledine
|
5710ea6475
three more cases where maybe we want to exclude
|
14 years ago |
|
Roger Dingledine
|
9f47cfc21a
make formal a constraint that's been true a while now
|
14 years ago |
|
Roger Dingledine
|
2b5c39211c
refuse moria1.exit if moria1 is excluded
|
14 years ago |
|
Roger Dingledine
|
bcea155ce0
note another case where strictnodes is considered for exits
|
14 years ago |
|
Roger Dingledine
|
0ad3836f73
If ExitNodes and Exclude{Exit}Nodes overlap, obey Exclude{Exit}Nodes.
|
14 years ago |
|
Roger Dingledine
|
5d12495d98
the new entrynodes behavior is always strict
|
14 years ago |
|
Roger Dingledine
|
719b5b87de
don't exit enclave to excluded relays
|
14 years ago |
|
Roger Dingledine
|
7e2e8074d5
slight tweak on circuit_conforms_to_options
|
14 years ago |
