| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Part of #1241
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According to the spec, the publisher needs to periodically reupload the
descriptor.
```
Specifically, every time a hidden service publishes its descriptor, it also sets up a timer for a random time
between 60 minutes and 120 minutes in the future. When the timer triggers, the hidden service needs to
publish its descriptor again to the responsible HSDirs for that time period. [TODO SPEC: Control republish period
using a consensus parameter?]
```
After each `upload_for_time_period()`, the publisher now sets a timer as
described in the spec, by pushing a `ReuploadTimer` into its
`reupload_timers` heap.
Closes #1241
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
We will soon need the ability to trigger a descriptor reupload for a
specific time period.
Part of #1241
|
| | |
| |
| |
| | |
Will make the situation in #1264 clear, I think.
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
Something libtest is doing hides the child stderr/stdout from the test
log, when --nocapture is not given.
With these changes, I see much more output in failing cases or with
--nocapture. In the case mentioned in #1264, the message
"we survived raise SIGUSR2" is now printed both with and without --nocapture.
|
| |
|
|
|
|
|
|
| |
Don't try to name the type of `RLIMIT_FSIZE` in our tests:
its type is either `c_int` or `__rlimit_resource_t` depending on
the libc instance.
Closes #1264.
|
| |\
| |
| |
| |
| | |
Remove all semver.md files to start a fresh release round
See merge request tpo/core/arti!1957
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This crate has had new features added. It's 0.x. So bump in-tree
dependencies' references:
fs-mistrust
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bump the minor version of these crates, and update the in-tree
dependencies.
Recently published as fresh crates, let's just assume there are
breaking changes:
fslock-guard
test-temp-dir
Breaking API change affecting many many downstream crates:
tor-rtcompat
Downstream crates which we're (conservatively) assuming have
tor-rtcompat types in their APIs:
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-hspow
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-congestion
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
|
| |
|
|
| |
Discard hunks in examples/
|
| |\
| |
| |
| |
| |
| |
| | |
tor-keymgr: A handful of API fixes
Closes #1194 and #1074
See merge request tpo/core/arti!1948
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This will be used when a keystore race is detected.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
We are about to remove `KeyMgr::get_or_generate_with_derived`.
|
| | | |
|
| | |
| |
| |
| |
| | |
We don't store public HsId key in the keystore anymore, so this test is
not needed anymore.
|
| | |
| |
| |
| |
| |
| |
| | |
Now that `KeyMgr::generate` returns the generated key, we can tidy up
`get_or_gen_key`.
Part of #1074
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We will soon remove the `KeyMgr::*_with_derived()` functions, so we need
to rewrite `maybe_generate_hsid` using `KeyMgr::get` and
`KeyMgr::generate`.
An important point to note is that `maybe_generate_hsid` no longer
stores the `KP_hs_id` in the key store. The reason we originally put the
`KP_hs_id` in the keystore in the first place was to support offline
HsId mode. However, offline HsId mode was never fully implemented
(#1194), and the decision to put the public part of the HsId in the
keystore is controversial (#1195). We can revisit this decision when we
implement #1194, but for now, we don't need a separate `KP_hs_Id` entry
in the keystore.
|
| | |
| |
| |
| |
| | |
We're about to stop storing `KP_hs_id` in the keystore, so in
preparation, let's update the callsites that attempt to retrieve it.
|
| | |
| |
| |
| | |
We're about to stop storing the public part of the hsid in the keystore.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This simplifies the publisher code in preparation for #1241
This replaces the overly complicated task-based approach to
rate-limiting with a simpler one, where the publisher has:
* a separate `RateLimited` state that indicates it is rate-limited,
and for how long
* an additional arm in its `run_once()` `select_biased!`, which
checks if the rate-limit has expired
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
We _do_ schedule the rate-limited upload at `now +
UPLOAD_RATE_LIM_THRESHOLD`, see `schedule_rate_lim_upload()`.
|
| |/
|
|
|
| |
This shouldn't be a warning (it's logged when the reactor is shutting
down, not when it crashes).
|
| |
|
|
| |
Closes #1261.
|
| |\
| |
| |
| |
| |
| |
| | |
Add some higher-level documentation for tor-hsservice.
Closes #1228
See merge request tpo/core/arti!1945
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Closes #1228.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The onion service keys now live in the `hss/<nickname>` subdirectory
within the keystore.
This layout change is **not** backwards-compatible, so if you want to
use your existing hidden service keys, you will need to manually move
them to `<keystore_root>/hss`.
Closes #1260
|
| | | |
|
| | |
| |
| |
| | |
Mandatory use line shuffling.
|