| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This crate is meant to provide rate-limited log messages
to tell users about problems that can happen too frequently
to log individually.
This version is based off an earlier design, and off of
conversations with @diziet. It still needs tests.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Added macro for StorageConfig expand dir
See merge request tpo/core/arti!1728
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti-client test: add clippy exception
See merge request tpo/core/arti!1745
|
| |/ / / /
| | | |
| | | |
| | | | |
This clippy rule appears to be enabled by default in Rust 1.74.0
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
tor-hsservice: Generate revision counters using an OPE scheme.
Closes #1053
See merge request tpo/core/arti!1744
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This code was identical to that from `read_blind_id_keypair`.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This will soon be used in `publish/descriptor.rs` too.
|
| | | | |
| | | |
| | | |
| | | | |
generate_revision_counter.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This code is no longer needed: we're now using
`generate_revision_counter()` to generate revision counters using the
OPE scheme from appendix F.2 rend-spec-v3.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The publisher now generates revision counters according to the "encrypted time
in period" scheme described in appendix F.2 rend-spec-v3.
Part of #1053
|
| | | | |
| | | |
| | | |
| | | | |
Part of #1053
|
| | | | |
| | | |
| | | |
| | | | |
`period` is actually a `TimePeriodContext`, not a `TimePeriod.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
periods.
Hidden services can have multiple "active" time periods for which they
generate descriptors. We need to be able to compute the offset of a
timestamp from the start of a given time period, even if that timestamp
falls within the "next" time period (for example, when publishing
descriptors for the "previous" time period, the `when` timestamp will
fall outside the `(start, end)` range of the "previous" time period).
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Implementation for AES-based Order-preserving encryption
See merge request tpo/core/arti!1741
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is the approach from appendix F.2 in rend-spec.
Part of #1053.
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Specifically, we check nothing except the port.
This matches the behavior of C-tor and the documentation in
torspec!179.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is in keeping with the behavior of C tor, and of
torspec!179.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
update rustc for reproducible builds
See merge request tpo/core/arti!1743
|
| | | | | |
| | | | |
| | | | |
| | | | | |
otherwis it fails when it gets scheduled on a non-ipv6 ready runner
|
| |/ / / / |
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
Send less information in onion service BEGIN messages
Closes #1077
See merge request tpo/core/arti!1738
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
While looking for differences, we found that C tor always
omits the flags and the hostname from a BEGIN message sent on an
onion service circuit. In torspec!179, we specified that behavior.
This patch brings arti into conformance.
Closes #1077.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Upgrade a couple of dependencies
See merge request tpo/core/arti!1736
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
(rusqlite fails with time 0.3.18, which is the version it claims
to require.)
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Upgrade to clap 4
See merge request tpo/core/arti!1735
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove webpki cargo_audit exception
See merge request tpo/core/arti!1737
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
Apparently webpki came out of retirement and actually fixed
RUSTSEC-2023-0052. Versions >=0.22.2 should be fine.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Adapt handshake traits for ntor-v3
See merge request tpo/core/arti!1720
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Before version 10.6, `Shake256Reader` is incorrectly defined using
`Shake256Core` instead of `Shake256ReaderCore`. As a result, attempting
to instantiate `Shake256Reader` fails at compile time.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|