| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I generated this using C tor (latest main) and a Chutney network
about a week ago.
The subcredential is:
78210A0D2C72BB7A0CAF606BCD938B9A3696894FDDDBC3B87D424753A7E3DF37
The HS_blind_id is:
43CC0D62FC6252F578705CA645A46109E265290343B1137E90189744B20B3F2D
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Also, explain why a few of these certificates aren't actually useful
as certificates. (This issue is also documented in torspec!110)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This allows us to run `is_valid_at` and friends on the certificate
itself, which we will use soon in hsdesc validity checks.
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
tor-netdoc: Suppress a cfg-dependent dead code warning
See merge request tpo/core/arti!998
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is dead code when
cargo +stable clippy -p tor-netdir --all-features --all-targets
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
tor-linkspec: LinkSpec parsing: use read_nested_u8len
See merge request tpo/core/arti!1007
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | | |
This eliminates hardcoded length values.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-netdir: Use typed-index-collections for router status index
See merge request tpo/core/arti!1004
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Always use "index" and not "position".
Remove wording which is otiose given the type name.
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
Call it everywhere instead of the inherent method on MdConsensus.
(Verified by ad-hoc temporarily renaming MdConsensus::relays().)
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Fix a couple of minor issues
See merge request tpo/core/arti!1003
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is dead code when
cargo +stable clippy -p tor-netdir --all-features --all-targets
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/issues/756
I think this is going in the wrong direction, but it is better to fix
it so that the names agree for now, pending a decision on the naming.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Report causes of errors
Closes #680
See merge request tpo/core/arti!997
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Split off for ease of review and possible rebase.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
No functional change, just using the new idiom.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With safe logging disabled, print the error too.
With safe logging enabled, do not print the message or the error.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Requring `Display` is wrong here, because if this is actually an
Error, Display would be wrong because it doesn't display causes.
As it happens, the `error` parameter is only ever `&str`.
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
We want to call ErrorReport::report() on Errors, but this isn't an
Error but only a string.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Bump crate versions in preparation for 1.1.1.
See merge request tpo/core/arti!1001
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In !948 we renamed a couple of accessor functions, which is a
breaking change in `tor-cell`'s API.
In retrospect, perhaps we should have deprecated the old names and
added the new ones, so we wouldn't have to break the API. (This is
the only API break AFAICT since 1.1.0.)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These crates had API or behavior changes that may affect downstream
crates. Fortunately, they're all version 0.x, and don't need minor
bumps for this.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These changes influence behavior, but not effect compatibility.
(If I messed up, and any crate except for `arti` has non-breaking
API changes, that's still fine, since they are all version
0.x.)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These crates have not had changes to their behavior; as such it is
not necessary to bump their dependencies to require the new versions.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
It was erroneously created in the wrong place.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
We no longer use it anywhere; there is no reason to keep publishing
updates to it.
|
| | |/ /
|/| | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Run cargo update in preparation for release tomorrow
See merge request tpo/core/arti!1000
|