| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| | |
This commit introduces FixedB16U which is a FixedB64 pedant for B16U.
It will be required for ExtraInfoDigests.
|
| | |
| |
| |
| |
| | |
This commit adds a round-trip test for NumericBoolean to ensure that 0
is false and 1 is true.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit adds a new type, NumericBoolean, which implements
NormalItemArgument in order to be parseable with parse2.
It works very simple, namely it can be used to decode/encode a boolean
as a `0` (false) or `1` (true) which is found in a few places around
tor-netdoc.
The reason why this is its own type instead of implementing
NormalItemValue for the bool primitive is, that booleans are special
numerical types and to be future-proof against other oddities, a
separate wrapper type makes most sense.
|
| |\ \
| |/
|/|
| |
| | |
tor-netdoc: cargo feature rationalisation, phase 1
See merge request tpo/core/arti!3910
|
| | |
| |
| |
| |
| |
| | |
Part of #2492 phase 1.
No semver note because this is an experimental feature.
|
| | |
| |
| |
| |
| |
| | |
Part of #2492 phase 1.
No semver note because this is an undocumented transitional phase.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Because of the sorting requirement and the fact that a `KeyMgr` can have
multiple Ntor keys, the caller now explicitly extract the two Ntor keys
it wants from the `KeyMgr` and then creates a `RelayNtorKeys` object
with them.
Future changes (#2495) will move this into a view and warn if there are
more than 2 keys.
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| | |
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| | |
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| | |
Signed-off-by: David Goulet <[email protected]>
|
| |/
|
|
|
|
|
|
|
| |
This is when we get them from the keystore so we can have a concept of
ordering in the SmallVec.
Future commit will transform this into a struct handling both keys.
Signed-off-by: David Goulet <[email protected]>
|
| |\
| |
| |
| |
| | |
Fix new warnings from Rust 1.95
See merge request tpo/core/arti!3902
|
| | |
| |
| |
| |
| | |
Rust 1.95 warns us that this is an experimental API that could be
stabilized in the future.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Geoip: Move the data into the .data segment completely, and into an out-of-tree crate.
See merge request tpo/core/arti!3900
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This is perma-unstable: We'll use it to make an export tool,
but that's it.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This lets us guarantee that every bit sequence is a valid
Option<CountryCode>.
|
| | | |
| | |
| | |
| | |
| | | |
This change allows us to provide the parts of the DenseRangeMap
on the data segment.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This abolishes the NetDefn type, and turns DenseRangeDb into a map to
one or (optionally!) two types.
For the DBs we ship, which don't have asn information, this saves
about 2.5 MiB.
(It also probably saves a bit more, since the niche optimization
didn't apply to NetDefn as it existed before, since it tried
to distinguish Some(None,None) from None.)
|
| | | |
| | |
| | |
| | |
| | | |
This required correcting some errors in our previous
ersatz geoip databases.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This type is more space-efficient than RangeInclusiveMap
in the case where most ranges do not have gaps between them.
|
| | | |
| | |
| | |
| | |
| | | |
See torspec#401 and
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3864#note_3397715
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3864#note_3397714
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now it follows, rather than precedes, the parse2_impls and
encode_impls modules that it imports things from.
Pure code motion apart from deleting the todo.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is going to be used for encoding too.
|
| | | |
| | |
| | |
| | | |
We don't need the helper struct for this.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We're going to want this macrology to generate a encoder
implmeentation too. It's most convenient to make this its own module,
separating it from parse2_impls.
Enable the module if encoding is enabled, decorating its
parsing-related contents with the appropriate cfg.
Use pub(super) to export the encoding-related imports, so that we
don't end up with endlessly duplicated import lists.
Now there is place where we can put the encoder.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Start a new encode_impls module.
The pub(super) will be used in a moment.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is what we did for authcert.rs and it worked well there.
|
| | | | |
|
| | | | |
|
| | | | |
|