| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Applies the suggestion from
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3829#note_3388033
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
As suggested by @Diziet
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Closes #2427
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
This is now used by `Account::add_parent()` too.
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
I am moving this to another function because we'll soon need to run
these same checks in the new `Account::add_parent()` API I'm planning on
adding for #2427.
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
tor-proto: Change an error from `CircuitClosed` to `NotConnected`
Closes #2421
See merge request tpo/core/arti!3825
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | |_|_|_|/ / / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Returning `CircuitClosed` isn't right here since the circuit may not
have closed.
|
| |\ \ \ \ \ \ \ \ \
| |_|_|_|_|/ / / /
|/| | | | | | | |
| | | | | | | | |
| | | | | | | | | |
tor-netdoc: Use new unquoted meta syntax for deftly attributes
See merge request tpo/core/arti!3856
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The `doctype_for_error` attribute needs immediate adjustment, because
a string expression value is expected. With `quoted retain`, that
would be re-interpreted, silently. This kind of thing is why
`quoted rigorous` exists.
So change its docs and the one use site.
The macros' docs, and the other calls ites, we'll deal with shortly.
|
| |/ / / / / / / / |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
chutney CI: add hidden services
See merge request tpo/core/arti!3858
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Primarily to get recent improvements to bootstrap checking and
reporting.
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
In particular to help debug arti#1907
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| |_|_|_|/ / / / /
|/| | | | | | | |
| | | | | | | | |
| | | | | | | | | |
tor-proto: Lower log level of "removing circuit leg"
See merge request tpo/core/arti!3859
|
| |/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This appears often in the arti logs, but is a normal thing to happen.
|
| |\ \ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
tor-proto: Allow sending DATA cells on closed streams
Closes #2434
See merge request tpo/core/arti!3824
|
| | |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Previously we would close the circuit, which isn't great because there
can be other streams in use on the circuit.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Microdescriptor parsing using parse2
See merge request tpo/core/arti!3797
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Co-authored-by: Ian Jackson
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This commit documents that a u16 overflow in a certain branch is
impossible due to the properties of a BTreeSet over which an iteration
takes place.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Co-authored-by: Ian Jackson
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Callers now have to use PortRange::new which checks the input.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This commit refctors PortPolicy to use the new PortRanges, alongside
removing the now duplicate code.
The new PortPolicy implements ItemValueParseable, which makes it
possible to nicely parse it. Unfortunately, we cannot derive it
directly, because we do not store the RuleKind but instead parse it and
then invert the ranges in order to save space. However, internally this
is derived using a wrapper type from which we extract from.
The old FromStr implementation continues to be as bad as it has always
been because improving it would likely introduce more bugs than it would
solve, given that the legacy implementation has been there since forever
basically.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This commit copies the logic found in portpolicy.rs into its parent
module, namely into a type called PortRanges. Most of the code was
copied one by one, with only slight adjustments having been done.
The compression and inversion logic is the same though.
The purpose of this is to implement ItemArgumentParseable on this, which
is not really possible with a Vec<PortRange> because the port policies
have a weird format: Semantically they consist of multiple arguments
(i.e. multiple port ranges) but syntactically they are encoded as a
single netdoc argument, because there are no spaces in between.
|