| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| | |
release: Bump release date for 2.3.0.
See merge request tpo/core/arti!3953
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
release: Version bumps
See merge request tpo/core/arti!3952
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
cargo set-version -p arti-client 0.42.0
cargo set-version -p arti-config 0.42.0
cargo set-version -p arti-relay 0.42.0
cargo set-version -p arti-rpc-client-core 0.42.0
cargo set-version -p arti-rpcserver 0.42.0
cargo set-version -p arti-testing 0.42.0
cargo set-version -p arti-ureq 0.42.0
cargo set-version -p tor-async-utils 0.42.0
cargo set-version -p tor-basic-utils 0.42.0
cargo set-version -p tor-bytes 0.42.0
cargo set-version -p tor-cell 0.42.0
cargo set-version -p tor-cert 0.42.0
cargo set-version -p tor-cert-x509 0.42.0
cargo set-version -p tor-chanmgr 0.42.0
cargo set-version -p tor-checkable 0.42.0
cargo set-version -p tor-circmgr 0.42.0
cargo set-version -p tor-config 0.42.0
cargo set-version -p tor-config-path 0.42.0
cargo set-version -p tor-consdiff 0.42.0
cargo set-version -p tor-dirclient 0.42.0
cargo set-version -p tor-dircommon 0.42.0
cargo set-version -p tor-dirmgr 0.42.0
cargo set-version -p tor-dirserver 0.42.0
cargo set-version -p tor-error 0.42.0
cargo set-version -p tor-events 0.42.0
cargo set-version -p tor-general-addr 0.42.0
cargo set-version -p tor-geoip 0.42.0
cargo set-version -p tor-guardmgr 0.42.0
cargo set-version -p tor-hsclient 0.42.0
cargo set-version -p tor-hscrypto 0.42.0
cargo set-version -p tor-hsrproxy 0.42.0
cargo set-version -p tor-hsservice 0.42.0
cargo set-version -p tor-key-forge 0.42.0
cargo set-version -p tor-keymgr 0.42.0
cargo set-version -p tor-linkspec 0.42.0
cargo set-version -p tor-llcrypto 0.42.0
cargo set-version -p tor-log-ratelim 0.42.0
cargo set-version -p tor-memquota 0.42.0
cargo set-version -p tor-memquota-cost 0.42.0
cargo set-version -p tor-netdir 0.42.0
cargo set-version -p tor-netdoc 0.42.0
cargo set-version -p tor-persist 0.42.0
cargo set-version -p tor-proto 0.42.0
cargo set-version -p tor-protover 0.42.0
cargo set-version -p tor-ptmgr 0.42.0
cargo set-version -p tor-relay-crypto 0.42.0
cargo set-version -p tor-relay-selection 0.42.0
cargo set-version -p tor-rpcbase 0.42.0
cargo set-version -p tor-rpc-connect 0.42.0
cargo set-version -p tor-rtcompat 0.42.0
cargo set-version -p tor-rtmock 0.42.0
cargo set-version -p tor-socksproto 0.42.0
cargo set-version -p tor-units 0.42.0
|
| | | | |
|
| | |/ |
|
| |\ \
| |/
|/|
| |
| | |
Release prep (fixup-features)
See merge request tpo/core/arti!3949
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 9447e48d0c698d51c75706d5efedcd6142c82f2a, which
told Clippy to ignore a warning that (I think) no longer occurs.
(Clippy was complaining that we were _naming_ a function in a
const-context that wasn't const-stable at our MSRV. But it's fine
to _name_ a non-const function in that case: we just can't _call_
it.)
See https://github.com/rust-lang/rust-clippy/issues/15792 for more
info on the clippy bug.
AFAICT the warning no longer appears with current beta, nightly,
or stable versions.
|
| |\
| |
| |
| |
| |
| |
| | |
Upgrade to hickory-proto 0.26.1
Closes #2517
See merge request tpo/core/arti!3942
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes
https://rustsec.org/advisories/RUSTSEC-2026-0120.html
and
https://rustsec.org/advisories/RUSTSEC-2026-0119.html
Neither of these is relevant for Arti, but we may as well upgrade.
This change required some code changes, since the upgrade from 0.25
changed some of the old APIs.
Closes #2517.
|
| |\ \
| |/
|/|
| |
| | |
Unknown keyword handling fixes; use a more principled type for directory signature hash algo
See merge request tpo/core/arti!3923
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This type is now directly suitable for use in directory signatures.
While we're changing its type, rename the digest algorithm name field
from `digestname` to `digest_algo`. (The spec says `algorithm` but I
don't think we're going to reuse `direcctory-signature` for non-RSA
signatures so this is just the hash algorithm.)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We want DirectorySignatureHashAlgo for prod's directory Signature
type.
However, for complex cfg gate and macro scoping reasons, we can't just
move the definition out of poc. Hence this rather unpleasant
intermediate state. This will go away, and become normal again, when
we can abolish poc's signatures and have poc use a prod signature
type.
Review with
git show --color=always --color-moved-ws=allow-indentation-change --color-moved
|
| | | |
|
| | |
| |
| |
| |
| | |
We're going to use this for `directory-signature`'s hash algorithm,
which the current code always treats as a string!
|
| | | |
|
| | |
| |
| |
| |
| | |
Make the operation of disregarding the possible existence of
already-discarded information, more explicit.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows implementing NormalItemArgument for types that can only be
parsed, or only displayed - or other combinations.
I noticed this restriction while inventing a type I later decided was
unnecessary. I still think it's a good change.
There is no practical impact elsewhere, since in practice downstream
code implements NormalItemArgument rather than relying on it.
|
| | |
| |
| |
| |
| |
| |
| | |
Part of #2492 phase 3.
This feature was experimental, so now that there are no cfg use gates,
we can abolish it right away.
|
| | |
| |
| |
| | |
Part of #2492 phase 2.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-cert: stabilise/abolish "encode" feature, and fix builder naming
See merge request tpo/core/arti!3926
|
| | | |
| | |
| | |
| | | |
This was experimental. Everything gated by it has been stabilised.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is widely used in-tree already. I don't think it makes sense to
feature-gate it.
There are some (perhaps rather thin) tests for both the Ed25519Builder
and EncodedRsaCrosscert.
It is possible we might want to change the API further, but this is
still a 0.x crate so that's not going to be a problem.
We'll remove the actual cargo feature in the next commit.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Change all call sites.
This completes the rename.
|
| | | |
| | |
| | |
| | | |
Abolish the type alias and change call references.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a perfectly ordinary builder type. There isn't any reason why
it ought to be called "constructor". And, nowadays, we have things in
tor-netdoc called Constructor that take a different approach.
Briefly, leave a temporary compat alias, to make diffs more comprehensible.
Currently this experimental, so no semver implications.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Preperation work for upcoming tor-dirserver test refactoring
See merge request tpo/core/arti!3931
|
| | | |
| | |
| | |
| | |
| | | |
This is required to do some signature validation on legacy types in an
upcoming commit.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If extra-infos is set to NULL, which might be the case for micro
descriptors or even router descriptors because the field is optional
there, this SQL query fails because it cannot LEFT JOIN
server.extra_unsigned_sha1 when this field is NULL.
To fix this, we simply add an additional clause to the WHERE statement
that filters such rows out.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit changes the schema to make the fingerprint optional.
Reason for this is, that microdescriptors are also stored in this table
and microdescriptors only contain an OPTIONAL onion-key, meaning it may
not always be possible to determine this value from a microdescriptor,
thereby making it silly to require it here.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
linkspec: Add serde(default) to fields in RelayIds.
See merge request tpo/core/arti!3933
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With this change, we will accept serialized RelayId representations
that omit one or more keys. This will eventually allow us to omit
absent keys when we serialize these.
This is the first stage of #2477.
|
| |\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
tor-netdoc: Un-gate many features
See merge request tpo/core/arti!3930
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is needed because we don't have !3926 in main yet. It will
produce a semantic conflict when that merges.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change "ns-vote" gates to "incomplete":
* `vote` modules, and in the variety macro.
(And make a TODO more likely to be found.)
Change "parse2" gates to "incomplete":
* VoteAuthoritySection
|
| | | | |
| | | |
| | | |
| | | | |
Everything that this needs is un-gated now.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
These are complete. Un-gate the RouterStatusMdDigestsVote
implementation, and the export of both.
|
| | | | |
| | | |
| | | |
| | | | |
As per #2492.
|
| | | | |
| | | |
| | | |
| | | | |
As per #2492.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is only used for hsdescs right now. But it doesn't need to be
gated behind encode.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This stabilises the parse2 and encode impls of consensus tyepe:
* {plain, md}::{Preamble, RouterStatus, RouterStatusIntroItem}
It also un-gates the parse2 and encode impls of some vote types.
* VoteAuthorityEntry - this type has been completed.
* RouterStatusMdDigestsVote - whole type still gated with ns-vote
Re the remaining vote types (vote::*): although each_variety.rs
doesn't have a cfg itself, there is a feature gate in the variety
macrology.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This stabilises the parse2 and encode impls of
* Lifetime
* ConsensusMethods
* SharedRandStatus
* ConsensusAuthorityEntry
All of these are complete.
|
| | | | | |
|