| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
NetParams: Document its role as a validated config parameter
See merge request tpo/core/arti!492
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
export coverage to pages
See merge request tpo/core/arti!489
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
see https://gitlab.torproject.org/tpo/core/arti/-/issues/400#note_2800763
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
* Except for safelog and fs-mistrust, which are new.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(This is okay because we haven't published it yet, or any crate that
uses it.)
|
| |/ / / / |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Switch to derive_builder_arti_fork
Closes #446
See merge request tpo/core/arti!490
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For reference, the git source for this crate (and the others in its
workspace) currently lives in my personal github account (ijackson).
If this fork turns out to be long-lived and gains features and/or
users, it would be good to move it to a gitlab somewhere.
I have granted Nick crate ownership on the crates.io system.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Implement a safe-logging facility.
Closes #189
See merge request tpo/core/arti!485
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Here we add a config option to disable safe logging, and ensure that
safe logging is disabled when we are formatting an error message on
exit (since we assume it's safe to write sensitive info to stderr.)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This specifically applies the `sensitive` wrapper in the places
where we're logging target addresses at level "info" or higher.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a rough first-cut of an API that I think might help us with
keeping limited categories of sensitive information out of our logs.
I'll refine it based on experiences with using it.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Fix typos (using the typos-cli tool).
See merge request tpo/core/arti!486
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Make config builders, not validated structs, [de]serialize
See merge request tpo/core/arti!487
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Builders additionally derive: Debug, Serialize, Deserialize.
* Validated structs no longer derive: Serialize, Deserialize
and all related attributes deleted.
* As a consequence, all the `#[serde(deny_unknown_fields)]`
are gone. That means that right now unknown fields are totally
ignored. This is good for compatibility but poor for useability.
Doing something better here is arti#417, in progress.
* As a consequence, delete tor_dirmgr::retry::default_parallelism.
(The default value was already duplicated into a builder attr.)
|
| | | | |
| | | |
| | | |
| | | | |
Having a consistent order will make the nest commit easier to read.
|
| |/ / /
| | |
| | |
| | | |
We want to be able to serialise as well as deserialise configurations.
|
| |/ / |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
FallbackDir: orports: Introduce and use VecBuilder
See merge request tpo/core/arti!474
|
| | | |
| | |
| | |
| | |
| | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/474#note_2800481
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
And drop the ad-hoc orport() method. This brings FallbackDir's
orports field in line with our list builder API.
The general semver note in "configuation" seems to cover most of this.
|
| | | |
| | |
| | |
| | | |
This avoids it having to recapitulate defaulting logic.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is for lists of plain types (non-builder types).
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This allows us to use this with an item builder type which doesn't
impl Default. (Obviously this only makes sense for items which aren't
actually builders.)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is Quite Vexing that we have to use [ ] rather than the < > around
the generics, particularly given that we are also using [ ] to signal
"this is arrayish".
Signed-off-by: Ian Jackson <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The docs were a lie. $docs_and_attrs was missing from the expander.
And add a note about how any supplied docs are handled.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
GuardUsage: restrictions: Use list builder
See merge request tpo/core/arti!475
|
| | | | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Although these do not appear in the config, it does have a builder.
It seems sensible to get rid of this ad-hoc list manipulation site,
and replace it with our standard list builder API.
define_list_builder_helper requires that the builder element type be
Deserialize. Currently GuardUsageRestriction is a transparent, public
enum, so we aren't really exposing anything.
We could introduce GuardUsageRestrictionBuilder now, but
since it's not in the config and thereofore only in the public API of
the lower crates, we can definitely put that off.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
CI: Check that the lockfile is up to date.
See merge request tpo/core/arti!484
|