mirrors/arti.git/crates/tor-proto, branch arti-v1.1.13mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.132024-02-05T16:13:29ZBump minor versions2024-02-05T16:13:29ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T16:13:29Zurn:sha1:af615d87e20d0984f493dfb8dda7b0654d8d7304
Bump the minor version of these crates, and update the in-tree
dependencies.
Recently published as fresh crates, let's just assume there are
breaking changes:
fslock-guard
test-temp-dir
Breaking API change affecting many many downstream crates:
tor-rtcompat
Downstream crates which we're (conservatively) assuming have
tor-rtcompat types in their APIs:
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-hspow
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-congestion
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
Run maint/fixup-features2024-02-05T13:55:19ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T13:55:19Zurn:sha1:760dad9e1e2f4cd40f709d489e7fb454057592bb
Discard hunks in examples/
Mark lower-level hs-service features non-experimental2024-01-23T18:24:21ZNick Mathewsonnickm@torproject.org2024-01-23T18:24:21Zurn:sha1:0aa5e86e8f9c023b1b776d6a7f23af686e1a9208Merge branch 'send_incoming_request_failures' into 'main'2024-01-17T18:27:09Zgabi-250gabi@torproject.org2024-01-17T18:27:09Zurn:sha1:572078cd57fc3a916d7d4cc9a2ad3dfcd2d13fd8
Several clean-ups around failures in incoming stream request handlers.
Closes #1190, #1189, and #1188
See merge request tpo/core/arti!1892Remove TODO for #11912024-01-17T16:19:54ZNick Mathewsonnickm@torproject.org2024-01-17T16:19:54Zurn:sha1:25258bfc1061429f99a62426d41824be29d46df1
The bug described here was already fixed as #1065 via !1681.
Closes #1191.
proto: Use log_ratelim to report problems delivering BEGIN messges.2024-01-17T14:25:56ZNick Mathewsonnickm@torproject.org2024-01-17T14:25:56Zurn:sha1:c5478deab5b8bb4a1ea55946483bad948ff9eca0Give an error on duplicate call to allow_stream_requests.2024-01-17T14:00:34ZNick Mathewsonnickm@torproject.org2024-01-17T14:00:34Zurn:sha1:8bff4734d70bc1260cfd5fdfb230e479b79065fc
Closes #1190
proto: Close circuit _intentionally_ when Request Sink is dropped.2024-01-17T13:45:54ZNick Mathewsonnickm@torproject.org2024-01-17T13:45:54Zurn:sha1:163aec238f5cba8434826130d5637f6ae3a24a4b
In theory, it might be better to just un-register the
IncomingStreamRequestHandler when the Receiver for the stream
requests is dropped. However, there are two reasons not to do so:
1. It's tricky. We never actually poll on the corresponding Sink,
so there isn't a place where the Reactor would expect to get a
prompt notification of closure. We only find out that the
Receiver has been dropped when an attempt to send on the Sink
returns an `is_disconnected` error.
2. It's unnecessary. In the Tor protocols, once we have decided to
accept incoming stream requests on a circuit, we want to continue
to do so until one of the parties closes the circuit.
I've documented this in several comments, in case whe want to get
fancier in the future.
Closes #1188.
proto: Send END when buffer of IncomingRequests is full2024-01-17T13:16:48ZNick Mathewsonnickm@torproject.org2024-01-17T13:16:48Zurn:sha1:428285a3b9df515e25a4b4265950b3a0fc788430
Closes #1189.
proto: Convert a TODO HSS to ticket #11912024-01-10T15:04:27ZNick Mathewsonnickm@torproject.org2024-01-10T15:04:27Zurn:sha1:ca44209c77d2c1267c3fe9e5a0fa707e88e5868b