| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | | |
`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.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Before version 10.6, `Shake256Reader` is incorrectly defined using
`Shake256Core` instead of `Shake256ReaderCore`. As a result, attempting
to instantiate `Shake256Reader` fails at compile time.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use consistent phrasing when describing the two key fields to make it
clear they're referring to the same relay.
|
| | |/ / /
|/| | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
tor-keymgr: Minor doc improvements
Closes #1066
See merge request tpo/core/arti!1731
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
The module is private so it won't show up in the public docs.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We don't really need it.
Closes #1066
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
tor-circmgr: Port tests to MockRuntime
Closes #1090
See merge request tpo/core/arti!1727
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
MockSleepRuntime wraps a MockRuntime instead of using
test_with_one_runtime!(), so the tests should be more
deterministic
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The tests still use MockSleepRuntime for the more complicated tests
where we forcefully make one or both futures time out, but
MockSleepRuntime wraps a MockRuntime instead of using
test_with_all_runtimes!(), so the tests should be more
deterministic
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The funky thing was getting rid of the Canceled error from the channel
and returning the actual error from build_owned() properly
|
| | | | | |
|
| | |/ /
| | |
| | |
| | | |
build_modest_timeout() and build_huge_timeout() don't pass yet
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make conversation::send_message work without an error.
Closes #1085
See merge request tpo/core/arti!1726
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously it was possible for `handler` to be None only when
`msg` was also None, which would make SendMsgAndInstallHandler into
a no-op. Now, if `msg` is present but `handler` is absent, we
use the previously installed handler, which I think was our
intention.
Without this patch, `Conversation::send_message` simply won't work.
Fixes #1085.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
(We already require that it is Send when the client gives it to us
in circuit.rs, but we had previously forgotten that when we stored
it in the Reactor.)
|