| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | hsrproxy: test actual outputs of builder. | Nick Mathewson | 2023-09-19 | 1 | -1/+10 | |
| | | ||||||
| * | hsproxy: reject configurations with unreachable patterns. | Nick Mathewson | 2023-09-19 | 2 | -3/+53 | |
| | | | | | | | | This implementation uses rangemap to detect _all_ unreachable patterns, which might be a little overkill, but it's actually simpler to write it this way than to use an O(N^2) search to make sure that no pattern is covered by a _single_ previous pattern. | |||||
| * | hsrproxy: Say "one", not "single" to avoid confusion. | Nick Mathewson | 2023-09-19 | 1 | -1/+1 | |
| | | ||||||
| * | hsrproxy: repair emptyportrange behavior | Nick Mathewson | 2023-09-07 | 1 | -0/+2 | |
| | | ||||||
| * | hsproxy: add TODO link to thread. | Nick Mathewson | 2023-09-07 | 1 | -0/+3 | |
| | | ||||||
| * | hsprproxy: add note about possible validation step | Nick Mathewson | 2023-09-07 | 1 | -0/+2 | |
| | | ||||||
| * | hsrproxy: tests for (not accepting) legacy ipv4 formats | Nick Mathewson | 2023-09-07 | 1 | -0/+17 | |
| | | ||||||
| * | hsrproxy: Add todos about udp and haproxy | Nick Mathewson | 2023-09-07 | 1 | -1/+9 | |
| | | ||||||
| * | hsrproxy: Refactor ProxyPattern to use RangeInclusive. | Nick Mathewson | 2023-09-07 | 1 | -50/+33 | |
| | | | | | | Also, allow nonempty ranges starting with 0- and implement Eq and PartialEq. | |||||
| * | hsrproxy: Make config member pub(crate). | Nick Mathewson | 2023-09-07 | 1 | -1/+1 | |
| | | ||||||
| * | hsrproxy: implement builders and serde. | Nick Mathewson | 2023-09-07 | 2 | -5/+75 | |
| | | ||||||
| * | hsrproxy: implement parse/encode for patterns and targets. | Nick Mathewson | 2023-09-07 | 2 | -5/+257 | |
| | | ||||||
| * | Create a tor-hsrproxy crate to handle "proxy to local port". | Nick Mathewson | 2023-09-07 | 4 | -0/+134 | |
| I'm calling this a "reverse proxy" since I think a lot of folks like that terminology, though I'm not personally a huge fan. Calling it "`tor-hsproxy`" would IMO confuse people more about what kind of proxy it was. This is a separate crate from `tor-hsservice` because it's logically at a different level: if you're writing a little embedded onion service, you don't need this code. Right now there is only configuration logic here. | ||||||
