mirrors/arti.git/crates/tor-hsrproxy/src/proxy.rs, branch arti-v1.2.7 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7 2024-08-28T14:27:46Z extract tor_async_utils::oneshot into ::oneshot-fused-workaround 2024-08-28T14:27:46Z Jim Newsome jnewsome@torproject.org 2024-08-22T19:20:36Z urn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1 Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency. hsrproxy: Temporarily remove ability to config unix addresses 2024-01-16T16:56:28Z Nick Mathewson nickm@torproject.org 2024-01-16T16:56:28Z urn:sha1:36dcbe9382e12f32d2aecb159c8b51c14871a701 I'm taking this out for now since we don't have support for actually making these addresses work, and the current behavior will just ignore connections silently. Closes #1245 hsrproxy: downgrade remaining TODO HSS comments. 2024-01-09T19:59:18Z Nick Mathewson nickm@torproject.org 2024-01-09T19:59:18Z urn:sha1:c062efb82ee26c538477b5ffd95c255246bfff44 Apply 1 suggestion(s) to 1 file(s) 2023-12-11T18:08:13Z Ian Jackson iwj@torproject.org 2023-12-11T18:08:13Z urn:sha1:19546723df1b94af599315b706c7068f60ca3c44 hsrproxy: Log rate-limited failures of other types as well 2023-12-07T21:56:39Z Nick Mathewson nickm@torproject.org 2023-12-07T21:52:27Z urn:sha1:bac9aa4508967b13ee552a95027e9dfdcd6a82e5 We separate these from our failures to connect to a local proxy, since that is a much more common error. hsproxy: remove TODO about retroactive limits 2023-12-07T21:42:10Z Nick Mathewson nickm@torproject.org 2023-12-07T21:42:10Z urn:sha1:89dc5a749ea9679d69ddef575371f4a7edb0efb8 See arti#1153 for followup work here. The current behavior is IMO a decent default. hsrproxy: Remove TODO about empty Connected messages 2023-12-07T21:15:56Z Nick Mathewson nickm@torproject.org 2023-12-07T21:15:56Z urn:sha1:d5af321c7e784c09c6d6c59e91d7b9cff725a1d5 See torspec!237 hsproxy: Add a rate-limited log for forwarding errors. 2023-12-07T16:32:01Z Nick Mathewson nickm@torproject.org 2023-12-07T16:30:06Z urn:sha1:428df5f77018d3ef7c5380bf4595618dca90d4e4 hsrproxy: Take nickname as an argument and pass it to forwarding function 2023-12-07T16:32:01Z Nick Mathewson nickm@torproject.org 2023-12-07T16:26:52Z urn:sha1:0a0f8e77880644688548b0847d2ccc3cabd0b36f We'll use this for logging. hsrproxy: Document what we check about begin messages 2023-10-23T15:51:59Z Nick Mathewson nickm@torproject.org 2023-10-23T15:51:59Z urn:sha1:779e12a1aae29370ad7e6f658d7a70c2d798e963 Specifically, we check nothing except the port. This matches the behavior of C-tor and the documentation in torspec!179.