mirrors/arti.git - mirror of https://gitlab.torproject.org/tpo/core/arti

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Run "fixup-features" on arti crates.	Nick Mathewson	2023-10-02	1	-1/+1
\|
*	tor-hsrproxy: Fix relative documentation warning	Emil Engler	2023-09-30	1	-2/+2
\| \| \| \| \|	This commit fixes a warning in the documentation, caused by an unresolved name.
*	hsrproxy: detect shutdown correctly.	Nick Mathewson	2023-09-27	1	-6/+23
\|
*	hsrproxy: improve error handling somewhat	Nick Mathewson	2023-09-27	2	-34/+113
\| \| \| \| \|	With this patch we now propagate errors upwards rather than handling them at the lowest possible level.
*	rproxy: Implement the actual "proxy" part of the code.	Nick Mathewson	2023-09-27	1	-10/+78
\| \| \| \| \|	Now we finally have the code to copy the data back and forth on the two AsyncRead+AsyncWrite objects that we create.
*	hsrproxy: Implement more of the proxy functionality	Nick Mathewson	2023-09-27	2	-4/+138
\|
*	hsrproxy: Start to sketch out an rproxy implementation.	Nick Mathewson	2023-09-27	4	-0/+79
\|
*	hsrproxy: rename Direct => Simple.	Nick Mathewson	2023-09-19	1	-21/+24
\|
*	hss: Rename ProxyTarget to ProxyAction.	Nick Mathewson	2023-09-19	1	-16/+16
\|
*	hsproxy: Revise configuration based on discussion	Nick Mathewson	2023-09-19	1	-41/+95
\| \| \| \| \| \| \|	We now have a single ProxyTarget action for the case where we accept a request and forward it: `Forward`. It takes an encapsulation method (currently only "direct") and a target address which can be inet or unix.
*	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.