| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
Without this there's no convenient way to add a transport without
messing with serde/toml.
Found while working on #791
|
| |
|
|
|
|
|
|
| |
The consensus seems to be the builders don't add much value, see [this comment].
[this comment]: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1070#note_2889488
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |
|
|
| |
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |
|
|
|
|
|
|
| |
`NetdocText` is a wrapper around a `String` and a type marker. The type
annotation proved of limited use, and made the netdoc builder API
somewhat awkward to use.
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |
|
|
| |
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Unlike `hsdesc::IntroPointDesc`, `hsdesc::build::IntroPointDesc`
represents link specifiers as `LinkSpec`s rather than
`UnparsedLinkSpec`s.
Since this is a general-purpose representation of an introduction point
and not merely an intermediate representation for decoding/encoding, it
will probably need to be factored out of `tor-netdoc` at some point.
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This introduces the `NetdocBuilder` trait described in
`netdoc-builder.md` and a new `tor-netdoc::doc::hsdesc::build` module,
which exports the `HsDescBuilder`. Hidden services will use
`HsDescBuilder` to build and encode hidden service descriptors.
There are several TODOs in the code that I'm planning to address
separately.
Partially addresses #745.
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |
|
|
|
|
|
| |
These are used in multiple places (and will also be used by the HS
descriptor encoder later on), so let's make them named constants.
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |
|
|
|
|
|
| |
This makes some code a bit more concise, as it allows us to make
`Strings` into `ItemArgument`s without calling `.as_str()`.
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |\
| |
| |
| |
| | |
Update required openssl version
See merge request tpo/core/arti!1077
|
| | |
| |
| |
| | |
cargo-audit is complaining about 0.10.45.
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Do minimal $ and ~ handling even without expand-paths and fix build
Closes #790
See merge request tpo/core/arti!1069
|
| | | |
|
| | |
| |
| |
| | |
Fixes #790
|
| | |
| |
| |
| | |
So, this is not a semver addition.
|
| | | |
|
| | |
| |
| |
| | |
str can always be made into a PathBuf.
|
| |\ \
| | |
| | |
| | |
| | | |
Bump to the lastest versions of dirs and directories.
See merge request tpo/core/arti!1072
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Closes #784.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1071/diffs?commit_id=580fe1118dbbbfa086d11b28e3e26d7c91afe21c#fbd7ab2d6d0a5b515697d4f9f99a42ebd508aa4b_153_165
|
| | | |
| | |
| | |
| | | |
I think this is uncontroversial; we already have it for Sensitive.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This avoids some dead code warnings when building without send-control-msg.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Here I use the name I propose in !1039.
|
| | | |
| | |
| | |
| | |
| | | |
Obviously this still doesn't work because the actual impl in hsclient
is just a todo!().
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We want this part for HS too.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We're going to want to reuse this.
Also: rename StreamPrefs::isolation and update the docs, to better
reflect its rather limited functionality. The new
TorClient::isolation is the only call site.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This seems more consistent with the way it's done elsewhere.
|
| |/ / |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This uncovered a bug: NoUsage wasn't correct for Hs circuits because
of its behavior with channel_usage().
|
| | | |
|
| | |
| |
| |
| | |
(Still, only expose it when experimental-api is enabled.)
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The prediction and scheduling logic here is quite primitive;
we should probably refactor it considerably. This should be good
enough for now, though.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We now have support for a pool of pre-build circuits that we can use
for HS-related purposes, and we take circuits from this pool as
needed.
Nothing populates or cleans the circuit pool yet.
|
| | |
| |
| |
| |
| | |
This is now enough to launch circuits on demand. It still needs to
pre-build the first three hops, and to retry on failure.
|
| | | |
|
| | |
| |
| |
| |
| | |
This only builds the first 3 hops. It can be extended to a fourth
hop later -- or not, depending on the circuit kind.
|
| |/
|
|
| |
We'll use this to implement the circuits used by onion circuits.
|