| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| | * | Fix Rustdoc errors. | Nick Mathewson | 2021-12-08 | 1 | -3/+3 | |
| | | | ||||||
| | * | Allow on-the-fly changing of path_rules | Nick Mathewson | 2021-12-07 | 1 | -0/+8 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | And now the complexity begins: when the user changes the path_rules, they not only want new circuits to obey those rules: they want _all new requests_ to be put onto circuits that obey those rules. That means that when the path rules become more restrictive, we need to retire all the circuits, and make sure that currently pending circuits aren't used for any requests. If it's any comfort, doing this was even more complicated in C tor. ;) | |||||
| * | | Don't create circuits if the consensus is stale by over 72 hours | Neel Chauhan | 2021-12-12 | 1 | -0/+4 | |
| |/ | ||||||
| * | Implement the guard side of shared state directories. | Nick Mathewson | 2021-10-21 | 1 | -1/+10 | |
| | | ||||||
| * | Actually select guards for directory circuits. | Nick Mathewson | 2021-10-13 | 1 | -0/+4 | |
| | | ||||||
| * | Integrate GuardUsability and GuardMonitor into CircuitBuilder. | Nick Mathewson | 2021-10-10 | 1 | -0/+5 | |
| | | | | | | | (When we're building a path with a guard, we need to tell the guard manager whether the path succeeded, and we need to wait to hear whether the guard is usable.) | |||||
| * | Add a GuardMgr member to CircuitBuilder | Nick Mathewson | 2021-10-10 | 1 | -0/+4 | |
| | | ||||||
| * | Move all crates into a `crates` subdirectory. | Nick Mathewson | 2021-08-27 | 1 | -0/+73 | |
| This will cause some pain for now, but now is really the best time to do this kind of thing. | ||||||
 |
index : mirrors/arti.git | |
| mirror of https://gitlab.torproject.org/tpo/core/arti |
| aboutsummaryrefslogtreecommitdiff |