| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
No behavior change.
Make the const cells public as they will be useful for more upcoming
unit tests especially on the relay side.
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti-relay: Log the public ntor key
See merge request tpo/core/arti!3882
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
We only need the max, not the entire sorted list.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is useful for testing.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Small cleanup.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Code movement only.
|
| | | |/ / /
| |/| | |
| | | | |
| | | | | |
Set up function placeholder.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
ci: Re-enable 'flowctl-cc' and 'counter-galois-onion' in arti-extra
Closes #2400 and #2416
See merge request tpo/core/arti!3889
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tor-proto: Fix stream XON/XOFF flow control sidechannel mitigation bug
Closes #2400
See merge request tpo/core/arti!3884
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If this is zero, then it means that the consensus had bad values.
But may as well check it anyways.
|
| | | | | | |
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-netdoc: parse2: Fix error for invalid item argument
See merge request tpo/core/arti!3879
|
| | |/ / /
| | | |
| | | |
| | | | |
When we can't parse a NormalItemArgument, that's Invalid, not Missing.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-netdoc: Improve B64 FixedB64 and B16
See merge request tpo/core/arti!3870
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
I also searched this file for FromStr impls and these types were the
only ones that ought to be NormalItemArgument but weren't.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Unfortunately one derive can't invoke another, so we must open-code
them, just like the other traits.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Nothing derives just Transparent yet.
Mostly code motion, with some additional furniture and docs.
Review with git show --color-moved.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This error message is going to be used by both Transparent and
BytesTransparent. Put it in the code that is going to be part of
Transparent, and remove the macro name from it.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This reduces clutter some more.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is in the use's at the top of the file. If we `use super::*`
(like we do in the newer modules): the code can get a lot more
readable.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Test the parsing and printing success cases.
Given that the parsing implementation is just a wrapper around B16's,
we don't need explicit tests for that.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Make this a public BytesTransparent newtype like B64, implementing all
the same traits etc.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On reflection, and looking at the test cases, I think the name `B16`
should refer to the lowercase version. I'll introduce a type for
uppercase in a moment.
Test the display implementation.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Replace the open-coded .parse() calls with a closure.
This will let us test round trips, other types, etc., for each pairs
of test values.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Firstly, make its field pub.
Secondly, make the into_array method crate-private. It has a
crate-specific (albeit public) error type, The same basic effect can
be achieved with methods from std on arrays and slices.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make this type public.
The new macro call means this type now implements many more traits.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
I think these are all the traits that a parsing/printing newtype
adapter ought to implement.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Actually make the macro be a proper d-d macro. Replace uses of .0
with $fname, B64 with $ftype, etc.
No functional change in this commit.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Break various open-coded impls on B64 into this macro. That will let
us reuse this code for other types, making all these bytes wrappers
similar to each other.
In this commit, we just move the code. The macro is wrong because it
ought to refer to $ttype and so on. Review with git show --color-moved.
No functional change in this commit.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is slightly more logical and will make the next commit slightly
easier to read.
|
| |/ / /
| | |
| | |
| | | |
This will reduce some duplication and simplify some macrology.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Tweak TunnelId and TunnelScopedCircId Display impls
See merge request tpo/core/arti!3875
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Circuit IDs (UniqId) are displayed as "Circ <x>.<y>".
Prior to this MR, these TunnelScopedCircId's were displayed as
"Circ <t>.<x>.<y>" where t is the integer tunnel ID. This made corresponding
logs a bit confusing as to why some "Circ" identifiers had two parts and
some have three, and didn't make clear that the "<x>.<y>" part of the latter
were comparable with the two-part UniqIds.
The previous commit effectively changes the latter to
"Circ Tunnel <t>.<x>.<y>", which is still a bit confusing.
This commit changes the display of TunnelScopedCircId's to "Circ <x>.<y>
(Tunnel <t>)", which makes the distinction between the circuit and
tunnel IDs clearer.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is akin to how circuit `UniqId`'s are prefixed with "Circ", and
helps clarify logs where it isn't always clear from context whether a
tunnel ID or circuit ID is being displayed.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Update to rand 0.90.3 and 0.10.1
See merge request tpo/core/arti!3880
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes RUSTSEC-2026-0097.
This is an unsoundness bug resulting from unexpected reentranccy if
the whole program contains both of the following
1. rand with the log feature enabled
2. logging hook that calls rand
Both of these are a priori quite unlikely. I checked with "cargo
tree" that our uses of rand do not end up depending on log, so I think
nothing in our tree enables the rand log feature.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-netdoc: ContactInfo
See merge request tpo/core/arti!3866
|
| | | | | | |
|