| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | |
| | |
| | |
| | | |
As discussed with gabi on IRC today.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some things I'm still considering here:
* We may want to define a tor_llcrypto::pk::rsa::Signature newtype.
* We likely want to rename tor_llcrypto::pk::rsa::PrivateKey to RsaKeypair.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove check_doc_features and doc_auto_cfg.
Closes #1514
See merge request tpo/core/arti!3294
|
| | | | |
| | | |
| | | |
| | | | |
This feature has been removed from nightly, in favor of doc_cfg.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that rust nightly has merged doc_auto_cfg into doc_cfg,
and completed https://github.com/rust-lang/rust/pull/138907,
it is no longer necessary.
Closes #1514.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
Fix two clippy warnings
See merge request tpo/core/arti!3295
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes
warning: struct `PossumCage` is never constructed
warning: associated function `make_cast_table` is never used
with
cargo +stable clippy --locked --offline -p tor-rpcbase --all-targets
Most of our builds happen with --all-features so we don't notice. In
that case I think something to do with method
printing:(`describe-methods`) is using things enough for the compiler
not to complain.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Sort output events for next_circ_action.
See merge request tpo/core/arti!3292
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This sort makes it so that that blocking and unblocking are always
ordered in a sensible way with respect to sending data. This might
help simplify padding machines a bit.
Prerequisite for #2190
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
chutney ci: reorganize scripts, especially configuration handling
See merge request tpo/core/arti!3264
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is partly just to get more code out of "main", but also paves the
way a bit for reusing this config code in the `integration-e2e-shadow`
wrapper script, to support the same command-line arguments there.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since we're validating the presence of jq, we might as well handle it
consistently with the other dependencies and provide a way to specify
where it is.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Encapsulate the logic of finding and validating each option into their
own objects (e.g. so that specification of corresponding command-line
option goes together with other related logic).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This wasn't a pre-existing environment variable, and now it can be set
via command-line if it needs to be overridden. I don't see much reason
to use an environment variable here.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We avoid much refactoring at this step to minimize functional changes
from the shell script.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes the `setup` script a bit more clearly single-purpose of
resolving and storing the configuration, without actually acting on it
yet.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It made sense to have this as part of the setup when the chutney network
itself didn't include arti; i.e. this used to be just validating the
non-chutney tor network before adding chutney nodes.
Now that the chutney network natively includes arti nodes, `chutney
verify` is testing those nodes; i.e., testing arti.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Add experimental OpenTelemetry support
See merge request tpo/core/arti!3239
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
It's unlikely these arguments will be particularly useful, and omitting
skip_all can have security implications, so it's better to avoid it to
reflect good practice.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We may want to add a way to opt out of this check, if someone asks for
it. Checking for "localhost" and "127.0.0.1" is not a very robust check
for a loopback interface, and it's possible that there could be other
situations we can't detect where HTTP is safe (private network,
WireGuard tunnel, etc). But I don't expect those to be likely to come up
in practice, so this should be fine for now.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
I've added these in places that are useful for the debugging that I've
been doing.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
netdoc parse2: Overhaul and many tests
See merge request tpo/core/arti!3231
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Should fix the minimal versions test?
|
| | | | |
| | | |
| | | |
| | | | |
Should fix the minimal versions test?
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will be used for some bits of netdocs where dummy values now
appear.
|