| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |/ / / |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Fix a rustdoc link in tor-netdir.
See merge request tpo/core/arti!647
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Refactor NetDirProvider APIs to better support timeliness.
Closes #518
See merge request tpo/core/arti!642
|
| | | |
| | |
| | |
| | | |
Its existence tended to hide bugs, and was just asking for trouble.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This allows us to give better errors in the case where bootstrapping
succeeds at first, but fails thereafter for long enough to make our
directory expire.
|
| | | |
| | |
| | |
| | |
| | | |
Everything here wants a timely directory, except that it is okay
to build timeout-testing circuits with a stale one.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Over the years we've found that most callers who want a netdir want
what C Tor calls a "reasonably live" network directory: One that is
not expired by too much, or too far in the future. But a few want a
_strictly_ live directory: one that says it is valid now, with no
tolerances. And a few want _any_ directory, no matter how expired
it is.
This commit adds net methods to NetDirProvider to provide these
directories. I think that most use cases will want to explicitly
think about what kind of directory they want, so I've made `netdir`
the simplest method. I might remove `timely_netdir` by the end of
this branch; see TODO comments.
Part of #518.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Rename DirSkewTolerance to DirTolerance, download_tolerance to dir_tolerance
Closes #503
See merge request tpo/core/arti!638
|
| | | |
| | |
| | |
| | | |
Closes #503.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This name is more accurate because we aren't only dealing with
clock skew here: we're also trying to tolerate the case where the
authorities fail to reach consensus for a while.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
use Ed25519 identity instead of PublicKey in tor-cert::rsa
Closes #512
See merge request tpo/core/arti!643
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
change usage of PublicKey to Ed25519 in tor-cert
Closes #512
See merge request tpo/core/arti!641
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
and propagate to other affected crates
|
| |/ / / |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Fix compilation of EstablishInto encoding.
See merge request tpo/core/arti!640
|
| |/ /
| |
| |
| | |
It was based on the old `Writeable` API.
|
| |\ \
| |/
|/|
| |
| | |
Implement ESTABLISH_INTRO relay cell
See merge request tpo/core/arti!626
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Clean-ups to error variants in arti-client
See merge request tpo/core/arti!637
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Downgrade phf back to 0.10
See merge request tpo/core/arti!636
|
| | | | |
|
| |/ /
| |
| |
| |
| | |
It turns out that phf 0.11 depends on Rust 1.60, which is above our
MSRV.
|
| |\ \
| | |
| | |
| | |
| | | |
Teach check_licenses to accept license on `unicode-ident`.
See merge request tpo/core/arti!635
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The license there is `(MIT OR Apache-2.0) AND Unicode-DFS-2016`,
which fine, but the existing shell script doesn't actually handle
"AND" correctly. This commit adds a workaround for licenses that
are "AND", and some comments about weaknesses in our (lack of)
boolean expression parsing.
This should fix CI.
|
| |\ \
| | |
| | |
| | |
| | | |
disable-fs-permission-checks: remove variable from help message
See merge request tpo/core/arti!633
|
| | | |
| | |
| | |
| | |
| | | |
This option doesn't take an argument. This change drops the argument
from the `--help` message.
|
| |/ / |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Move environment-variable checking into fs-mistrust
Closes #483
See merge request tpo/core/arti!630
|
| | | | |
|
| | | |
| | |
| | |
| | | |
These aren't user facing comments, but getting them
right will help us write better changelogs.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This logic can now be adjusted via the config object so that it does
its own overriding by looking at the environment as appropriate.
Removing these methods helps simplify the code a bit.
Enabled by #483.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that configuring the environment variables related to fs
permissions works properly, we don't need to use the "override"
feature any more: we can just add the option to the configuration
when appropriate.
With this design, `--disable-fs-permission-checks` is now mostly an
alias for
`--option storage.permissions.dangerously_trust_everyone=true`
Enabled by #483.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The variable is now handled when building the configuration, and no
longer needs to be special-cased.
Closes #483.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
By default we look at `$FS_MISTRUST_DISABLE_PERMISSIONS_CHECKS`.
Optionally, the user can provide another variable as well, or
disable looking at the environment entirely.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Revise tor_bytes::Writer::write to return a Result.
Closes #513
See merge request tpo/core/arti!623
|
| | | | | |
|