| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. Fix a use of 10ms that should have been TIMEOUT_SLOP.
2. Increase BODGE_YIELD by a factor of 5.
Now this test should tolerate being hung up for 125ms. I am hoping
that this will fix the CI failure
https://gitlab.torproject.org/Diziet/arti/-/jobs/302457
which fails at the line comparing circuit1 with circuit2a.
(I can't repro that locally.)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Without this, the expiry task can end up choosing a 600s timeout
starting *after we advanced the clock*.
Fixes #923
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The provided impl for Mutex is hopeless: it prints just some internal
flags and doesn't acquire the mutex for printing purposes.
At some point we might want to factor this out as a general function
on `Arc<Mutex<...>>` but not now.
|
| |\ \
| | |
| | |
| | |
| | | |
Upgrade to itertools 0.11.0
See merge request tpo/core/arti!1306
|
| | | |
| | |
| | |
| | | |
The breaking changes here do not seem to affect us.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-hsclient: Expire old IPT and HS descriptor data eventually
See merge request tpo/core/arti!1290
|
| | | |
| | |
| | |
| | |
| | | |
As per discussion in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1290#note_2915679
|
| | | |
| | |
| | |
| | |
| | | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1290#note_2915679
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1290#note_2915678
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1290#note_2915676
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a change to the API docs, but not to the actual code, since
our call site is in arti-client and tied to netdir fetch,
which *doesn't* happen when dormant.
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1290#note_2915677
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will allow us to track when `Data` is discarded.
|
| | | |
| | |
| | |
| | | |
Otherwise we'll fill up our RAM with junk.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove final "experimental" status from tor-hscrypto and tor-error.
See merge request tpo/core/arti!1291
|
| | | | |
| | | |
| | | |
| | | | |
The relevant ErrorKinds and macros are now stable.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Add TODO SPEC for issues dealt with in !1299
See merge request tpo/core/arti!1303
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-hsclient: Add a TODO SPEC re circuit dirtiness
See merge request tpo/core/arti!1302
|
| | | |_|/ /
| |/| | | |
|
| |\ \ \ \ \
| |/ / / /
|/| / / /
| |/ / /
| | | | |
Drop intro circuit after ack, and deal with TODOs
See merge request tpo/core/arti!1299
|
| | | | |
| | | |
| | | |
| | | | |
And delete the corresponding TODO.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-hsclient: Expire old IPT data
See merge request tpo/core/arti!1295
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This won't be trivial. Put it in as a TODO HS rather than as part of
this fix MR.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If we don't use it for a whole, the whole of `Data` will be expired by
the new machinery in !1290. However, we also need to expire
individual IPTs.
This bug doesn't seem to have had a relevant TODO.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
tor-hsclient: Expire circuits when they get too old
See merge request tpo/core/arti!1287
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| | |
We don't now handle inability to store by panicking. Like the
previous comment says, such situations end up with Err in stored,
and that's handled by logging, below.
|
| |\ \
| | |
| | |
| | |
| | | |
Clean up HsDesc error types and stabilize onion-service ErrorKinds
See merge request tpo/core/arti!1289
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These have been subsumed by other errorkinds, mostly
OnionServiceProtocolViolation and TorProtocolViolation.
In particular please review the change in tor-hsclient closely;
I am not sure about the new errorkinds for the error there.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For higher-level HsDesc-related functions, this type indicates where
exactly an error occurred. It lets us distinguish decryption errors
from parsing errors, and attribute responsibility to the hsdir, the
onion service, or the user's lack of encryption.
This lets us remove some just-introduced complexity in
tor-hsclient.
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Generate correct-ish socks5 errors for onion service errors.
Closes #736
See merge request tpo/core/arti!1279
|
| | | |
| | |
| | |
| | | |
Part of #736
|