| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Update all lint blocks
|
| |
|
|
| |
of the proxy port.
|
| |\
| |
| |
| |
| |
| |
| | |
Implement support for reachable_addrs
Closes #491 and #93
See merge request tpo/core/arti!583
|
| | |
| |
| |
| | |
(This doesn't do anything yet.)
|
| |\ \
| | |
| | |
| | |
| | | |
Use impl_standard_builder more and remove manual Default/builder impls
See merge request tpo/core/arti!594
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Config handling and logging fixes
Closes #480
See merge request tpo/core/arti!589
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Prompted by review
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/589#note_2813596
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Right now this is an IEFI and therefore a no-op.
|
| | | | |
| | | |
| | | |
| | | | |
It contains only sections, but we want to detect when that is a problem!
|
| | |/ /
| | |
| | |
| | | |
We're going to call this new closure another time.
|
| |\ \ \
| | |/
| |/|
| | | |
# Conflicts:
# crates/arti-client/Cargo.toml
|
| | |\ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Add "full" and "experimental" features to arti, arti-client, and below.
Closes #499
See merge request tpo/core/arti!584
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rustls uses ring, which uses code from BoringSSL, which derived from
OpenSSL before OpenSSL changed their license. So ring is currently
under 3BSD/SSLEay licenses, which aren't GPL-compatible, which may
be a problem for some people.
See #493.
|
| | | |
| | |
| | |
| | |
| | | |
As per point 1 in
https://gitlab.torproject.org/tpo/core/arti/-/issues/488
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
These need to be optional: they improve performance by shifting to
asm implementations, which may not be everybody's idea of good practice.
These are not 'pure' features, since they select one implementation
but disable another. Therefore they don't go in `full`.
Closes #441.
|
| |/
|
|
|
| |
Also, unify the features documentation format for those two crates,
and document previously undocumented features there.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
lints: Make lint blocks consistent and ensure they stay that way
Closes #469
See merge request tpo/core/arti!557
|
| | |
| |
| |
| | |
The remaining consequences of running add_warning
|
| | |
| |
| |
| |
| | |
From running add_warning, with manual picking of the right
hunks/lines.
|
| | |
| |
| |
| | |
These need to survive.
|
| | |
| |
| |
| |
| |
| | |
This was the result of:
maint/add_warning crates/*/src/{lib,main}.rs
and then manually curating the results.
|
| | |
| |
| |
| | |
This is the final piece of #457.
|
| | |
| |
| |
| |
| | |
This allows us to add the proper default example to the arti example
config file.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now the validated configuration will never be `Some(0)`, even if that
is what was written in the config file. The arti CLI parser can still
produce this, so we don't touch the code that actually uses this.
(Without the canonicalisation the default builder produces `None` for
the `dns_port`, but the example would produce `Some(0)`, which is
semantically identical but fails the test.)
See https://gitlab.torproject.org/tpo/core/arti/-/issues/488 for some
background.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Canonicalise the `logging.journald` setting in the validated
configuration. Now it will never be `Some("")`, even if that is what
was written in the config file.
This allows us to write `journald = ""` in the example configuration.
(Without the canonicalisation the default builder produces `None` and
the example would produce `Some("")`, which are semantically identical
but fail the test.)
See https://gitlab.torproject.org/tpo/core/arti/-/issues/488 for some
background.
|
| | |
| |
| |
| |
| | |
These weren't previously discussed. It's not practical or useful to
show the actual default values here.
|
| | |
| |
| |
| | |
Found by my forthcoming test.
|
| | |
| |
| |
| |
| | |
This makes the config default parser see just "[ ]", an empty list,
which is indeed the default.
|
| | |
| |
| |
| | |
That this remained was an oversight.
|
| |/ |
|
| |\
| |
| |
| |
| | |
add unit tests for ArtiConfig public functions
See merge request tpo/core/arti!551
|
| | |
| |
| |
| |
| | |
this change adds some simple tests for the ArtiConfig public getter
functions to help expand coverage in this crate.
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Break TorClientConfig out of ArtiConfig and warn on unknown config keys
Closes #459 and #417
See merge request tpo/core/arti!529
|
| | | |
|
| | |
| |
| |
| |
| | |
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 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 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.
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
This change requires a little refactoring of TorClientBuilder: now,
instead of enabling or disabling mistrust, it enables or disables
the decision to _override_ the mistrust in the config.
|