| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This makes it possible to parse2 micro descriptors, which will be very
useful later on.
For this, it makes a few changes. Most notably, it introduces a
(private) field called `onion_key`, which stores an optional RSA onion
key, as it serves as the introduction line for this netdoc document
type. Besides, it also changes the `ed25519_id` type to the
`Ed25519IdentityLine` wrapper type, although the signature of the
respective getter remains the same.
|
| |
|
|
|
|
| |
This is a sane default, because rejecting all ports is the default for
relay configurations as well as the default of when this field is absent
in netdocs.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This commit implements ItemValueParseable for PortPolicy. Unfortunately
we cannot use NormalItemArgument because it contains spaces, leading to
multiple arguments.
In a later commit, we may migrate this fully to parse2 because right
now, it just wraps around its FromStr implementation.
|
| | |
|
| |
|
|
|
|
| |
This commit replaces the inner value of RelayFamily to use a LongIdent
instead, which it already uses for parsing, in order to derive
ItemValueParseable on it, so we can use it within parse2 magic.
|
| |
|
|
|
|
| |
This commit makes LongIdent parseable by implementing NormalItemArgument
as well as the required Display for it. Besides, it also derives Hash
on it.
|
| |
|
|
|
|
|
|
| |
This commit improves upon B64 by implementing NormalItemArgument for it,
as well as implementing a wrapper type for it, called FixedB64, that
works just like B64 except that the resulted inner-value must be of a
certain compile-time-specified fixed length, which is useful for things
such as digests.
|
| |
|
|
|
|
|
|
|
|
| |
Now some bugs have become visible.
* Properly ``-quote the name in the heading.
* Add a missing space before `{`
* Adjust the fields to level-4 indent.
* In `construct()`, ``-quote the name, and xref it in the body,
not the title (which rustdoc makes a link to the fn itself)
|
| |
|
|
|
|
| |
This lines all the docs lines up, so we can see our indentation.
No change to the generated docs.
|
| |
|
|
| |
No change to the generated docs.
|
| |
|
|
| |
No change to the generated docs.
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3851#note_3388076
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This was just some type aliases. Put them in the poc files that used
them. (These type aliases are undesirable but we aren't cleaning them
up because the whole of poc is destined for deletion.)
|
| |
|
|
|
| |
Get rid of the version in poc. Instead, implement the same
functionality in terms of AuthCert::verify, outside poc.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
These are in fact just a completely normal RSA signature like in the
spec!
Move the type to the types module, and rename it. Leave a
compatibility alias.
|
| | |
|
| | |
|
| |
|
|
| |
This will allow us to use it for encoding as well as parsing.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
We mustn't use selector.selector() because that's for multiplicity,
not optionality. In pracctice, it goes wrong with Vec<u8>.
|
| | |
|
| |
|
|
| |
This was a c&p error, I think.
|
| | |
|
| |
|
|
|
|
| |
The hidden __non_exhaustive field has to be pub.
And, fix the use site, currently AuthCert.
|
| |
|
|
| |
Otherwise deriving NetdocEncodable doesn't work outside this crate.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This method verifies all the signatures, and checks that the signing
authority is in the provided list. Anyway, authcerts aren't really
self-signed: they're a signature by KS_auth_id_rsa on
KP_auth_sign_rsa.
Note that there is also a `verify_selfcert` method which does only
some of the checks, and has some code duplication. That will be
cleaned up later.
|
| |
|
|
|
|
|
|
|
|
|
| |
With the introduction of the derives for document encoding, we now
have a trait ItemObjectEncodable. We will want a method on
ItemEncoder that takes an ItemObjectEncodable, and that should be
called `object` since it's a better approach than working ad-hoc with
tor_bytes::Writeable. (For example, an ItemObjectEncodable knows its
own label.)
So, rename `object` to `object_bytes`.
|
| | |
|
| | |
|
| |
|
|
|
| |
This commit lno_for_error in ItemStream to lno because its value may not
always be used for error handling, such as in tor-consdiff.
|
| |
|
|
|
|
|
|
|
| |
This commit adds the ParseError::new() method, which allows external
APIs to construct a ParseError, which is currently not possible due to
non-exhaustiveness, despite the member fields being public.
It is required for external applications using lower-level but public
parse2 APIs, such as ItemStream's.
|
| |
|
|
| |
Typos found with codespell
|
| | |
|
| |
|
|
| |
Suggested-by: Clara Engler <[email protected]>
|
