| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
I keep finding I want to encode things and then I have to prat about
with a NetdocEncoder. Let's provide potted versions.
|
| |\ \ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | | |
tor-netdoc testdata-live: Export for the benefit of other crates
See merge request tpo/core/arti!4229
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add a new testdata_live module which is exposed with the testing
features, containing the testdata-live in string constants.
This avoids the need for test cases in other crates to walk the
filesystem to an area outside their own crate path.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We're about to *use* the fix that was in 1.11.4. We already updated
the lockfile in !4228, so this is just Cargo.toml changes (which will
prevent the minimal-versions tests failing when we change the code to
rely on the fix).
git-grep -l '^derive-deftly' |xargs perl -i~ -pe 's{\b\Q1.11.3\E\b}{1.11.4}g'
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This updates everything, but really I'm just running it to create the
new selected_relays.rs file.
The meaning of this file will become clear shortly.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We could use build.rs for this, but since we have a script already,
this seems better.
The meaning of this file will become clear shortly.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Move supported consensus methods iteration to tor-dirauth from arti-dirauth
See merge request tpo/core/arti!4234
|
| | | |/ / /
| |/| | |
| | | | |
| | | | | |
Now we provide SupportedConsensusMethod::iter_all().
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
integration-e2e-shadow: initialize network outside of shadow
This is progress towards generating multi-host simulations; we want to use the generated network specification when generating the shadow config, so the former has to happen before we start shadow.
Progress on #1683
See merge request tpo/core/arti!4211
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This keeps everything together and avoids clobbering previous artifacts,
since chutney already creates a unique nodes dir in every run.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes the chutney network configuration available *before* we
generate the shadow config file, which we need in order to generate
multi-host networks.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is in preparation to move the init step outside of the shadow
simulation in integration-e2e-shadow (while leaving the bootstrap step
inside the shadow simulation).
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is in preparation to diverge somewhat. In particular, we want to do
some of the configuration and setup from *outside* of shadow, so that
we can generate shadow configs that take the chutney network
configuration into account.
|
| | | | | | | |
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti: Ratelimit proxy error reports
See merge request tpo/core/arti!4158
|
| |/ / / / /
| | | | |
| | | | |
| | | | | |
Implement log_ratelim! in report_proxy_error
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
proto: Remove feature-gating from CircHop::handle_msg()
See merge request tpo/core/arti!4230
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This can happen if we get an unexpected BEGIN_DIR/RESOLVE too, so we
can't hard-code "BEGIN" in the error message.
Context: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4230#note_3439258,
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This feature-gating has been a source of confusion, and it unnecessarily
complicates the stream message handling flow.
I've previously argued in favour of keeping it, in the spirit of a belt
and braces approach to message validation, but I've been convinced that
in this particular case, the feature-gate is more trouble than it's
worth.
What makes things worse is that the `CircHop::handle_msg()`
function was designed poorly (by yours truly). I plan on refactoring it
at some point, hopefully soon. There is a TODO about this below
its doc comment.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti-dirauth: Build an arti consensus method plugin binary, and implement list-methods
See merge request tpo/core/arti!4225
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will appear when the MR is merged.
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4225#note_3439197
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4225#note_3438787
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4225#note_3438786
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Although we have other places in-tree where we do this very standard
thing, we don't seem to have an affordance for it. I doubt we want to
add a dependency just for this, so roll our own.
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | | |
This just panics, right now.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-dirmgr: Refactor function download
See merge request tpo/core/arti!4204
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Add helper functions: perform_download, advance_state, apply_state, and
update_state
- Add enum used in said helper functions: DownloadOutcome and AdvanceStateError
- Add minor improvements on the readability of the entire sub-module
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
hashx: Update dynasmrt to 5.1.0
Closes #2637
See merge request tpo/core/arti!4232
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This was forgotten in the previous commit.
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes a rust future-incompatibilities warning, which was caused by
the proc-macro-error2 crate.
The dynasmrt crate switched to a fork proc-macro-error3 to fix this.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tor-cert-x509: Fix RSA key size check
Closes #2626
See merge request tpo/core/arti!4231
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Overhaul tor_checkable's TimeBound
See merge request tpo/core/arti!4223
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4223#note_3438348
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4223#note_3438344
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4223#note_3438341
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|