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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove "publish=false" from tor-hsrproxy.arti-v1.1.10	Nick Mathewson	2023-10-31	1	-2/+0
\|
*	Patch version bumps in crates without breaking changes	Nick Mathewson	2023-10-31	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	``` These crates have new APIs: tor-async-utils ADDED tor-config ADDED tor-hscrypto ADDED tor-netdoc ADDED, plus BREAKING-experimental. These crates have patch-level changes only: tor-netdir (bugfix only). (re-exposes netdoc) arti-rpcserver (tweaks only, uses nothing that broke.) arti 1.1.10, no stable public APIs. ```
*	Minor version bumps in crates with breaking changes.	Nick Mathewson	2023-10-31	1	-4/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	``` tor-basic-utils BREAKING tor-rtmock BREAKING. tor-cert BREAKING tor-cell BREAKING tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental) tor-chanmgr BREAKING: Re-exposes proto. tor-ptmgr BREAKING: re-exposes tor-chanmgr tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?) tor-circmgr BREAKING: re-exposes proto tor-dirclient BREAKING tor-hsclient BREAKING, re-exposes proto. tor-hsservice BREAKING, re-exposes proto. tor-hsrproxy BREAKING arti-client BREAKING: re-exposes proto. arti-hyper: BREAKING, re-exposes arti-client. tor-dirmgr Let's assume BREAKING, very high-level. tor-keymgr BREAKING, but experimental. ```
*	Run "fixup-features" in preparation for release this week.	Nick Mathewson	2023-10-29	1	-1/+1
\|
*	oneshot: Use veneer in tor-hsrproxy	Ian Jackson	2023-10-11	1	-0/+1
\|
*	Non-working attempt to test onion service configuration.	Nick Mathewson	2023-10-03	1	-1/+10
\| \| \| \| \| \| \|	The problem here is that, for some reason, the proxy_rule configuration doesn't actually work. I suspect a bug in Flatten, since the same configuration works fine if you pass it to the hsrproxy config directly.
*	hsrproxy: Make configs and builders implement more traits.	Nick Mathewson	2023-10-03	1	-0/+1
\|
*	Minor-version bumps, for crates with breaking changes.	Nick Mathewson	2023-10-02	1	-1/+1
\|
*	Patchlevel bumps, with dependents affected.	Nick Mathewson	2023-10-02	1	-4/+4
\|
*	Run "fixup-features" on arti crates.	Nick Mathewson	2023-10-02	1	-1/+1
\|
*	hsrproxy: improve error handling somewhat	Nick Mathewson	2023-09-27	1	-0/+1
\| \| \| \| \|	With this patch we now propagate errors upwards rather than handling them at the lowest possible level.
*	hsrproxy: Implement more of the proxy functionality	Nick Mathewson	2023-09-27	1	-0/+5
\|
*	hsrproxy: Start to sketch out an rproxy implementation.	Nick Mathewson	2023-09-27	1	-0/+4
\|
*	hsproxy: reject configurations with unreachable patterns.	Nick Mathewson	2023-09-19	1	-0/+1
\| \| \| \| \| \| \|	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: implement builders and serde.	Nick Mathewson	2023-09-07	1	-0/+5
\|
*	hsrproxy: implement parse/encode for patterns and targets.	Nick Mathewson	2023-09-07	1	-0/+1
\|
*	Create a tor-hsrproxy crate to handle "proxy to local port".	Nick Mathewson	2023-09-07	1	-0/+22
	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.