| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |/
|
|
|
|
|
|
| |
There are incomplete pieces, marked with "TODO circpad".
There is no integration into the circuit reactor code yet.
Part of #63
|
| |\
| |
| |
| |
| | |
Require tracing-subscriber 0.3.20
See merge request tpo/core/arti!3221
|
| | |
| |
| |
| | |
Fixes RUSTSEC-2025-0055.
|
| |\ \
| |/
|/|
| |
| | |
various crates: Switch to "assert in const" pattern
See merge request tpo/core/arti!3217
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Replaced use of [`static_assertions::const_assert`] with the newly
available "assert in const" pattern. This completely removes the
dependency on `static_assertions` for `tor-netdir`.
Signed-off-by: hashcatHitman <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Replaced use of [`static_assertions::const_assert`] with the newly
available "assert in const" pattern. This completely removes the
dependency on `static_assertions` for `tor-circmgr`.
Signed-off-by: hashcatHitman <[email protected]>
|
| |/ |
|
| |
|
|
|
| |
We've promised in our README not to bump MSRV in patchlevel
releases. So now this is 1.5.0.
|
| |
|
|
|
|
|
|
| |
Per policy, we bump the minor version of every tor-*, arti-* crate
on each release.
We have updated our MSRV, so we're treating this as a breaking
change for our non-(arti/tor)-prefixed crates too.
|
| | |
|
| |
|
|
|
|
| |
Closes #2026.
We can do this now that criterion-cycles-per-byte has also upgraded.
|
| |
|
|
|
| |
Also, document why we are (for now) stuck using a tilde with our
ureq dependency.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Upgrade to toml-0.9.5.
Closes #2093
See merge request tpo/core/arti!3163
|
| | |
| |
| |
| | |
Closes #2093.
|
| |\ \
| | |
| | |
| | |
| | | |
smol: Implement smol in tor-rtcompat
See merge request tpo/core/arti!2986
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| |
| | |
This is so a relay can build authenticated channels. Several keys/cert
are required for this that are within the key manager.
Signed-off-by: David Goulet <[email protected]>
|
| |\ \
| |/
|/|
| |
| | |
More PoW miscellania
See merge request tpo/core/arti!3132
|
| | |
| |
| |
| |
| |
| | |
I'm not 100% on this being here, it seems like it might want to be a
option for all onion services, rather than per-service. However, this is
good enough for now.
|
| | | |
|
| |/
|
|
|
|
| |
testresult is a new dependency for arti.git. (It's being added as a
test-dependenchy here.) It is has a very useful Result type for use
in test cases.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoids
https://rustsec.org/advisories/RUSTSEC-2025-0047
I have considered whether this needs a TROVE. I think not.
We don't call the unsound method at all directly within arti.git.
As for our dependencies: I (with some flailing) managed to patch the
whole build to use a modified version of slab with the unsound method
sabotaged. This was successful. So I think nothing in our whole tree
uses it.
(I also verified that my sabotage arrangements were effective:
applying `#![cfg(any())]` at the top of slab's lib.rs did break the
build of hs.)
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
examples/hyper/hyper-http-client-example/Cargo.toml
examples/hyper/hyper-http-hs-example/Cargo.toml
In both cases, just the change of edition, which I have applied to
examples/hyper-examples/Cargo.toml
instead.
|
| | |
| |
| |
| |
| |
| | |
I had been planning to use `[]::is_sorted` here, once we had
MSRV >= 1.82, but it turns out that we wanted strictly ascending
sequence, whereas `is_sorted` checks for a non-descreasing sequence.
|
| | |
| |
| |
| |
| | |
(We were unable to do this before, since it required a rust version
we didn't have.)
|
| | |
| |
| |
| | |
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Introduce the new Tunnel structs that is planned to expose publicly as a
replacement to `ClientCirc`.
Future commits will make those tunnel objects be used accross the code
base up until tor-proto which than handles Circuit directly.
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| | |
This was accidentally omitted from my version bump script.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Made with the following shell script:
export CARGO='nailing-cargo -Eu'
# Non-functional changes only
maint/bump_nodep hashx
# Special
$CARGO set-version -p arti 1.4.6
# Additional features, no breaking changes, depended on in tree
$CARGO set-version -p safelog 0.4.8
# Unconditional bump to 0.33.0
xargs -I P <<END $CARGO set-version -p P 0.33.0
tor-error
tor-general-addr
tor-geoip
tor-rtcompat
tor-rtmock
tor-async-utils
tor-config
tor-config-path
tor-rpc-connect
tor-log-ratelim
tor-rpcbase
tor-memquota
tor-units
tor-llcrypto
tor-bytes
tor-protover
tor-checkable
tor-cert
tor-key-forge
tor-hscrypto
tor-socksproto
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-relay-selection
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
tor-relay-crypto
arti-client
arti-relay
arti-rpcserver
arti-ureq
arti-rpc-client-core
END
|
| | | |
|
| | |
| |
| |
| | |
No upstream changes that break our code.
|
| | | |
|
| |\|
| |
| |
| |
| | |
# Conflicts:
# examples/hyper-examples/src/bin/hyper-http-hs-example.rs
|
| | | |
|
| | |
| |
| |
| | |
Closes #2012.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This pulls in num_traits (which is already a dependency for PoW) to
allow f64 casts that for reasons I do not understand are not implemented
via TryFrom in the standard library.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
We will make a separate library for this.
|
| | |
| |
| |
| | |
This directory had to be renamed because otherwise it would cause conflicts with the actual hyper crate in the CI pipeline.
|
| | |
| |
| |
| |
| | |
This example directory had a separate directory for each example. We can
simplify this by using binaries.
|
| |/
|
|
|
| |
This example demonstrates how to create a custom connector which can be injected
into a hyper client, to use hyper for Tor requests.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* CLI: Add `keys-raw` and subcommand `remove-by-path`
* arti: Add `arti::subcommand::raw` for the CLI `keys-raw`
* tor-keymgr: Add `ArtiNativeKeystoreError::UnexpectedRawEntry`,
`ArtiEphemeralKeystoreError::NotSupported`
* tor-keymgr: Add `tor-keymgr::raw` module
* tor-keymgr: Add `Keystore::remove_unchecked`
* tor-keymgr: Change `Keystore::list` to return `KeystoreEntry`
* tor-keymgr: Add field `KeystoreEntry::raw_id`
* doc: Update keys.md
* doc: Add raw.md
* tor-keymgr: BREAKING: `UnrecognizedEntryError::new` associated
function is now only accessible within the crate `tor-keymgr`
* tor-keymgr: BREAKING: `UnrecognizedEntryId` is renamed to
`UnrecognizedEntry`
* tor-keymgr: BREAKING: `KeyMgr::list()` and `Keystore::list()`
now return `Result<Vec<KeystoreEntryResult<KeystoreEntry>>>`
|
| |
|
|
|
|
|
|
| |
Done using:
```
cargo set-version --bump patch -p arti
```
|
| |
|
|
|
|
|
|
|
|
| |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.32.0
done
```
|