| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This code has most of what we need to go from an INTRODUCE2 message
we've just received to the point where we've connected to the
rendezvous point and we're waiting for a stream of BEGIN messages.
Unfinished pieces are marked with TODO HSS.
Most of #980.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
| |
The IPT manager is going to want to separate the IptEstablisher
struct (which contains the Drop signal) from the watch receiver.
We could add an accessor to clone the watch, but the copy in the
IptEstablisher would be redundant.
This makes new()'s signature a bit funky but it's an internal method
so I think that's fine.
|
| |
|
|
|
| |
It now supports running in a loop, trying to establish an
introduction point, and reporting status.
|
| | |
|
| |
|
|
| |
This will help with making a keep_established method.
|
| | |
|
| | |
|
| |
|
|
|
| |
Intro points must not send these extensions except in response to a
request that prompts them.
|
| |
|
|
|
|
| |
I had planned to make this code accept extensions of unknown type,
but for now I'm backing out of that plan: the set of extensions we
send influences the set that we're willing to receive.
|
| |
|
|
|
|
|
|
| |
This should be enough now to establish real introduction points,
though there is still a lot of work to do. Part of #976.
This has been rebased and edited to incorporate discussions from
!1465.
|
| | |
|
| |
|
|
|
|
|
| |
As with the other APIs here, I'd expect that the implementors will
need to refactor this a lot.
Closes #972.
|
| | |
|
| |
|
|
|
|
|
| |
Taken from @diziet's !1439 and lightly cleaned up so that it
compiles.
Closes #971.
|
| | |
|
| |
|
|
|
|
|
| |
Also, removed some older structures that don't make sense in the
current design.
Closes #970
|
| |
|
|
|
|
|
|
| |
See here for documentation on the lint:
https://rust-lang.github.io/rust-clippy/master/index.html#/diverging_sub_expression
The issue here, from what I can tell, is that the lint triggers
whenever you use a diverging expression as a function body within an
|
| |
|
|
| |
These are all service-specific, and not client-specific.
|
| |
|
|
|
|
| |
The HS `HsClientSpecifier` and `HsClientSecretKeySpecifier` are moved to
`tor-hsclient`. The HS service secret key specifier stubs are moved to
`tor-hsservice`.
|
| |
|
|
|
| |
In order to store per-circuit information, it's a good idea if we
provide something that can be the key of a `PtrWeakKeyHashMap`.
|
| |
|