| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| | |
On Windows filenames are WTF-16, not bytes, so a weird filename fails
to be UTF-16 rather than failing to be UTF-8.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
The private ExpiryError type is now err::StateExpiryError.
We'll fix up the local alias in the HasKind impl in a moment.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
The non-visibility of this method seems like it must have been an
oversight.
|
| |/
|
|
|
|
| |
If one of the upload results is for an HsDir that went away, the
publisher should continue processing the remaining ones, not disregard
them entirely.
|
| |\
| |
| |
| |
| | |
tor-hsservice: Expire old on-disk IPT state
See merge request tpo/core/arti!1977
|
| | | |
|
| | |
| |
| |
| |
| | |
This test detects the bug mentioned here
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1977#note_2995265
|
| | | |
|
| | |
| |
| |
| | |
This isn't strictly necessary, but it's better.
|
| | |
| |
| |
| | |
This seemed to warrant some discussion and a cross-reference.
|
| | |
| |
| |
| |
| |
| | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1977#note_2994999
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1977#note_2995000
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1977#note_2994998
Removing the intermediate variable removes the possibility that the
information in it could fail to be transferred to the main mutable
state, so we don't need the IEFE any more.
|
| | |
| |
| |
| | |
We do have some tests, but they're not as comprehensive as we'd like.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Without this, we can regenerate the same IptLocalIds (etc.) on
shutdown/restart (which involves calling startup again within a test
case).
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Indentation left anmolaous briefly for ease of review.
|
| | |
| |
| |
| |
| | |
The expiry code is going to want this too. We should at least make a
constant of it.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We shouldn't keep the same IPT relays just because they're not
working! Firstly, that's just silly, and secondly, for privacy
reasons we want to put a limit on teh lifetime anyway.
Indentation left anmolaous briefly for ease of review.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
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.
|