| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These crates had only clippy fixes that do not affect their
behavior:
tor-bytes
tor-cell
tor-events
tor-linkspec
tor-netdir
tor-socksproto
This crate only had the cargo-husky dependency removed, which
does not affect compatibility:
tor-llcrypto
Since these changes have no compatibility effects, it is not
necessary to bump the versions of these crates which other crates
depend on.
|
| | | | | |
|
| | |/ /
|/| | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Add a few coverage-driven tests
See merge request tpo/core/arti!536
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Also, if we get an IoError from a call to fs-mistrust, report it as
an IoError.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Standardise shell
Closes #425
See merge request tpo/core/arti!533
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Break TorClientConfig out of ArtiConfig and warn on unknown config keys
Closes #459 and #417
See merge request tpo/core/arti!529
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We can have mem::take, hooray.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807331
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This was a slip.
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807330
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This makes the function a tiny bit clearer.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is not a doc comment because we don't want it to be public: it
must refer to private fields, etc.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Not available in our MSRV.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
I think this is a leftover from a previous version of this expression.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807070
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of the wrong "prefix_len". As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807068
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807078
This is in fact much clearer than the Option.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Split into its own commit to avoid churn in the rename commits.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807077
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per review comments
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807076
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This turns out to need quite a complicated algorithm.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This gets rid of `#[serde(flatten)]` which prevents serde_ignored (and
other kinds of introspection) from working properly.
The price is now that the toplevel has to deal with two configuration
objects.
The Resolvable trait is overkill right now, but is going to do More
Things in a moment. In particular, we need the impl on tuples, so
that the whole config can be processed in one go.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We are going to need this for some generic code which is going to
appear shortly. Having it produced by impl_standard_builder seems
best. But that does mean being able to disable it, so extra stuff in
the macro. Nothing uses this trait yet.
ConfigResolveError is not used now either, but will be in a moment.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We are going to reorganise ArtiConfig to not contain a
TorClientConfig. This test case's calls to bld.tor() will all need to
change. Do this in advance to make that future commit more readable.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I don't understand why this isn't tripping all the time. Maybe
because this is in a macro. Anyway, I am going to add a new
invocation of this macro from within a test where, empirically, it
trips.
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
ci: don't disable arti permission checks, fix resulting issues
See merge request tpo/core/arti!530
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
DirMgr:: Remove Error::NoChange as redundant.
Closes #484
See merge request tpo/core/arti!532
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now that the relevant functions now report changed/not-changed
status via a boolean out-parameter (see !527), there's no reason to
have a separate NoChanged error case.
Closes #484.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ConfigurationSources: Allow config files to be world-readable.
Closes #475
See merge request tpo/core/arti!528
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #475.
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
reply socks error on more codepath
Closes #258
See merge request tpo/core/arti!531
|
| | | |_|/ /
| |/| | | |
|