| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | |
| | | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/602#note_2830766
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit largely follows the example for resolve_alternative_specs.
The difference is that there are two fields, so we use a macro to
avoid recapitulating the field names.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will allow us to handle new kinds of warnigns etc.
|
| | | |
| | |
| | |
| | | |
We're going to want the to use the same type for deprecated keys.
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
arti: Raise the default console log severity to "info"
See merge request tpo/core/arti!692
|
| | |/
| |
| |
| |
| | |
Previously we logged at "debug", but that's not meant to
user-facing.
|
| | | |
|
| | |
| |
| |
| |
| | |
FoundConfigFile existed to hide something that ConfigurationSource now
exposes.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/682#note_2830860
And subsequent IRC discussion.
Having done the work as per review comments, I don't much like the
result. It's quite un-ergonomiuc. If we can't have fs autodetection,
I think syntactic autodetection within sources.rs would be nearly as
nice.
However, I seem to be outvoted. At least the externally visible
functionality (of an arti binary, say) is reasonably ergonomic.
|
| | | |
|
| | |
| |
| |
| | |
I think this ought to be exhaustive.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The parameter to FileWatcher::new is not a polling time fallback; it
is a "debounce time". Events are always delayed by at least this
much.
10s is much too long for this. 1s is more appropriate.
|
| | |
| |
| |
| | |
Fixes #474 aka #271
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We're going to need to do config file reading in two phases.
Right now this isn't actually necessary, because the set of files
is fixed since we don't support dynamically scanning directories.
But the new API will be needed in a moment.
Code motion and API changes, but no overall functional change.
Review with `git show -b` may be helpful.
The new API also provides for dealing with directories, but right now
that doesn't happen.
|
| | |
| |
| |
| |
| | |
We're going to want this functionality, which isn't in the stable
stdlib.
|
| | |
| |
| |
| |
| |
| | |
No call site just yet; that will come shortly.
This requires a bit of reorganisation first.
|
| | |
| |
| |
| | |
This is going to be needed in a moment.
|
| | |
| |
| |
| |
| |
| |
| | |
That way if the config changes after we read it initially, but before
we set up the watcher, we will still pick it up.
Fixes #544
|
| | |
| |
| |
| | |
This is going to become more complicated, and gain another call site.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previous approach (inherited from the API of notify) was kind of
odd.
Soon we are going to want to be able to drop the watcher and replace
it. That really wants the same object to contain all the things that
ought to be dropped together. (notify's watchers stop generating
events and give EOF on the channel, when dropped.)
|
| | |
| |
| |
| |
| |
| |
| | |
These blocks were in the wrong order.
Previously, if you tried to turn on process hardening in the config
and then reloaded rather than restarting, it wouldn't take effect.
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
arti_client: Refuse to build a client if we are setuid.
See merge request tpo/core/arti!689
|
| | |
| |
| |
| |
| |
| | |
Arti is not designed to be a setuid-safe program.
Part of #523.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
arti: Do not allow running as root.
See merge request tpo/core/arti!688
|
| | |
| |
| |
| |
| |
| | |
This can be overridden with `application.allow_running_as_root`.
Part of #523.
|
| |\ \
| | |
| | |
| | |
| | | |
Test oldest example configuration file
See merge request tpo/core/arti!684
|
| | | |
| | |
| | |
| | |
| | | |
Mostly cribbed from
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/684#note_2829937
|
| | | | |
|
| | |/
| |
| |
| | |
The defaults are now
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
At one point in this MR I thought I was going to want this for
arti::cfg::ListenConfig (which we don't want to be Default).
In fact ListenConfig is being handled specially, but having written
this function it seemed sensible to keep it. Since resolve_option
becomes a wrapper for it, the existing tests exercise it.
|
| |\
| |
| |
| |
| | |
Channel padding
See merge request tpo/core/arti!657
|