aboutsummaryrefslogtreecommitdiff
path: root/tor-proto
Commit message (Collapse)AuthorAgeFilesLines
...
* circuit: Remove the needlessly separated ReactorCore type.Nick Mathewson2020-10-231-29/+16
|
* channel: Remove the needlessly separated ReactorCore type.Nick Mathewson2020-10-231-21/+10
|
* Test for finish-handshake functionNick Mathewson2020-10-231-0/+18
|
* handshake: tests for invalid signaturesNick Mathewson2020-10-231-1/+49
|
* Add tests for handshakes certifying the wrong thingNick Mathewson2020-10-231-0/+53
|
* Tests for handshakes with missing certsNick Mathewson2020-10-232-11/+62
| | | | Also handle tor_cell::Error::ChanProto better.
* Use an enum for the return value of StreamMap::terminateNick Mathewson2020-10-222-8/+25
|
* Initial tests for tor_proto::circuit::streammapNick Mathewson2020-10-221-0/+51
|
* Tests for tor_proto::circuit::halfstreamNick Mathewson2020-10-221-1/+79
|
* tor-proto: Add tests for circuit::sendmeNick Mathewson2020-10-221-4/+134
|
* Add tests for tor_proto::circuit::celltypesNick Mathewson2020-10-211-0/+43
|
* Test a trivial succeeding case of link cert validationNick Mathewson2020-10-211-12/+72
|
* Fix a security issue (!) in link handshake validation.Nick Mathewson2020-10-211-1/+1
| | | | | | | | When making sure that the peer had the right RSA identity, we were comparing the RSA identity with itself, not with the RSA identity we expected. Found via unit testing (!).
* Infrastructure for testing handshake cert-validation codeNick Mathewson2020-10-211-1/+61
|
* More tests for handshake connect functionNick Mathewson2020-10-211-26/+136
|
* Start a basic test for the first part of the handshake.Nick Mathewson2020-10-211-0/+45
|
* LogId test: tolerate concurrent tests.Nick Mathewson2020-10-211-11/+8
|
* Start on some tests for pieces of tor-proto::channelNick Mathewson2020-10-214-0/+226
|
* Follow API convention about mutable getters.Nick Mathewson2020-10-212-8/+8
| | | | They're supposed to be called field_mut().
* Rename as_message to into_message.Nick Mathewson2020-10-211-1/+1
| | | | | According to the API guidelines, "as_" is only for borrowed->borrowed conversions.
* Add a close() method for streamsNick Mathewson2020-10-201-0/+8
|
* Add new `terminate()` method to circuits and channels.Nick Mathewson2020-10-202-6/+44
| | | | | | | | These aren't called "close" because they're more destructive than that: they can be called even if other parties are using the circuit or channel. This is for arti#21.
* Missing file and docsNick Mathewson2020-10-203-6/+45
|
* Add a TODO for register_meta_handler APINick Mathewson2020-10-201-0/+3
|
* Work on closing flooding-based side-channelsNick Mathewson2020-10-202-17/+28
| | | | | We need to make sure that we're dropping cells that we don't recognize or want, so that we can't be flooded with bogus junk.
* Add some helpful logs in circuit code.Nick Mathewson2020-10-204-15/+100
|
* Add reasonable logging (I hope!) to channelNick Mathewson2020-10-204-42/+219
|
* Implement From, not Into.Nick Mathewson2020-10-191-6/+6
| | | | | These traits are inverses of one another, but implementing From is always preferred since rust 1.41 relaxed the "orphan rules".
* Add and use remaining CertType values in tor-certNick Mathewson2020-10-191-2/+2
|
* Add an enumeration for destroy reasons.Nick Mathewson2020-10-191-3/+2
|
* Improvements to Relay type in tor-netdir.Nick Mathewson2020-10-191-1/+1
| | | | | | | | | | | Now, a Relay is always valid. This required some changes to the API: all_relays() has to return a new UncheckedRelay type that might or might not be valid, and the functions on Relay and ChanTarget that return ed25519 identities need to return an Ed25519Identity, not an ed25519::PublicKey. This change required some new encoding/decoding/conversion functions on Ed25519Identity.
* Mark must-resolve XXXX issues with "XXXXM3".Nick Mathewson2020-10-188-34/+30
| | | | | | | | | | "M3" is for "milestone 3" -- my target to fix the technical debt that I think will be bad if we ship even a pre-alpha with it. These aren't necessarily _all_ must-resolve, but they're all must-look-at. Closes #15
* tor-proto: Add a ClientCircChanMsg type.Nick Mathewson2020-10-155-22/+43
| | | | | | This wraps exactly the ChanMsg values that are valid on open client circuits, so that we can be sure that only those cells are sent to a ClientCirc's reactor.
* tor-proto: Add a "CreateResponse" type.Nick Mathewson2020-10-155-15/+64
| | | | | | CreateResponse includes exactly those cells that are a correct response to a CREATE2/CREATE_FAST, so we can be sure that only those cells are actually passed to a PendingClientCirc.
* Run "cargo upgrade".Nick Mathewson2020-10-151-2/+2
|
* Fix a couple of clippy warningsNick Mathewson2020-10-152-2/+2
|
* Turn the channel's ref to its circmap into a Weak referenceNick Mathewson2020-10-151-6/+11
| | | | | This way, when the channel reactor is dropped, the circuit map can get dropped too, which will cause reading circuits to notice.
* Mark channels as unusable if reactor gets an error.Nick Mathewson2020-10-153-1/+31
| | | | | Similarly as with circuits, we want this code to set a "closed" flag so that attempts to write on the channel will fail.
* Use weak references from circuit reactor to circimpl.Nick Mathewson2020-10-142-15/+30
| | | | This prevents the reactor from keeping the circuit alive forever.
* Use a weak reference from channel reactor to channel.Nick Mathewson2020-10-141-5/+7
|
* Send DESTROY cells when a circuit is dropped.Nick Mathewson2020-10-143-27/+161
| | | | | | | | | This reuses a lot of mechanism from the circuit code that sends END cells when streams are dropped. There is a problem here: Circuits and channels won't actually get dropped, because we should be using a weak reference from the reactor.
* Revise DropMark defense to use a better type and match Tor's behavior.Nick Mathewson2020-10-135-12/+97
|
* Document all private members in tor-protoNick Mathewson2020-10-1314-7/+131
|
* Make sure that protocol errors terminate the circuit responsible.Nick Mathewson2020-10-132-20/+55
|
* Improve handling of circuit closure or failure on reactor shutdown.Nick Mathewson2020-10-132-4/+35
| | | | | | | | | | We already handled the case okay when we were reading on streams, since the reactor's going away would drop the sender side of their mpsc channels. But if the reactor went away, nothing would tell _writing_ streams that they needed to close. Now we handle that case, as well as anybody who is waiting on a meta-cell to get back to them.
* Another tweak to handling closing streamsNick Mathewson2020-10-133-14/+40
| | | | | | When a stream is closed and we haven't adjusted its state in the stream map yet, remember how many cells we've dropped so we can decrement them from the window later on.
* Try giving distinct handling to streams where END has been sentNick Mathewson2020-10-125-51/+114
| | | | | | This is the first step along the line to handling Tor issue tor#27557. We want to remember streams that we've ended and treat them as distinct from streams that have never existed
* Tweak terminate hand handle_close() functions.Nick Mathewson2020-10-112-13/+20
| | | | | These need to become functions about terminating and noticing a termination request.
* Rename StreamMap::Closing to EndReceivedNick Mathewson2020-10-111-4/+4
| | | | This is in preparation for adding a different EndSent stream state.
* Fix a pair of bugs in SENDME handling.Nick Mathewson2020-10-091-13/+10
| | | | | | | | | The problem is that we would count begin and end cells towards towards window totals when we are only supposed to count DATA cells, *and* that we would we send our sendmes one cell too early (or maybe late?). Closes #1.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-28 04:41:28 +0000