| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
These crates both depend on tor-error. Since tor-error got a
patchlevel bump, they now depend on the new version, which means by
our rules that _they_ get a patchlevel bump themselves.
tor-geoip
tor-rpcbase
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This crate is new, and gets a bump to 0.1.0.
tor-log-ratelim
This crate had a breaking change:
tor-persist
tor-llcrypto had a breaking change. These crates _are_
tor-llcrypto, or (transitively) depend on it. I am assuming that
they all re-expose something from it in a way that matters:
tor-llcrypto
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-hyper
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These crates had backward-compatible changes, and get a patchlevel
bump only:
fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock
This crate exposes no non-CLI APIs, and gets a patchlevel bump only:
arti
|
| | |
|
| |
|
|
|
|
| |
This is not a change of ownership but just rebranding.
Signed-off-by: Andrew <[email protected]>
|
| |
|
|
|
|
|
| |
This version of the config crate includes a fix for the issue
(https://github.com/mehcode/config-rs/issues/464)
that had prevented us from using the format we had wanted for
our rproxy configuration.
|
| |\
| |
| |
| |
| |
| |
| | |
Convert to the latest versions of dalek-cryptography
Closes #808
See merge request tpo/core/arti!1767
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This code was needed with the old version of dalek-cryptography,
which wasn't compatible with up-to-date versions of the `rand`
crate(s). But now that we've upgraded, we can drop this.
(We could have left it around and deprecated it, but we are already
making a breaking change to tor-llcrypto by upgrading
dalek-cryptography.)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The main changes that we have to adjust for are as follows:
* In x25519-dalek:
* `StaticSecret` is now behind a feature.
* `StaticSecret::new` is deprecated in favor of
`StaticSecret::random_from_rng`.
* StaticSecret no longer does its own clamping.
* In ed25519-dalek:
* `SecretKey` has (in effect) been renamed to `SigningKey`. The name
`SecretKey` is now an alias for `[u8; 32]`.
* `SigningKey` is effectively a keypair, since it contains a
public key as well.
* `PublicKey` has been renamed to `VerifyingKey`.
* The functions to extract a signing key and verifying key have
been renamed as you might expect.
* `ExpandedSecretKey` has been moved to `hasmat` and no longer
implements `sign`.
* `ExpanededSecretKey` now has as its elements a scalar and a hash
prefix.
* Various functions that took `&[u8]` now take `&[u8; N]`.
* We no longer need a wrapper for older versions of rand.
There is a single test in tor-keymgr that does not pass. I've
marked it as ignore for now, in hopes that @gabi-250 can help me
figure it out.
This closes #808. There are several changes I want to make before
we merge, however. They are marked with TODO DALEK.
|
| |\ \
| |/
|/|
| |
| | |
tor-hsservice tests: Introduce new test_temp_dir helper module
See merge request tpo/core/arti!1762
|
| | |
| |
| |
| |
| |
| | |
While debugging IPT persistence I wanted to see what the code was
leaving in the storage and keystore directories. This is hard when
it's all done with a vanilla tempdir().
|
| |\ \
| |/
|/|
| |
| | |
Upgrade several crates in preparation for this month's release.
See merge request tpo/core/arti!1763
|
| | |
| |
| |
| | |
Gabi spotted that we weren't using this.
|
| | |
| |
| |
| |
| | |
This is a breaking change, since dirclient::Error
exposes http::Error.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
This avoids writing "[42,\n 43,\n ...]" into the storage json,
which is (a) wasteful (b) hard to read by hand.
|
| | |
|
| |
|
|
|
|
|
|
| |
tor-log-ratelim mistakenly had a non-path dependency.
Changing this, and running `cargo fetch --offline` to update the
lockfile, causes the build to prefer in-tree for many entries in the
lockfile.
|
| |\
| |
| |
| |
| |
| |
| | |
HSS: Send DosParams extension to introduction points.
Closes #723
See merge request tpo/core/arti!1740
|
| | |
| |
| |
| | |
It's available when the HsIntro=5 subprotocol version is present.
|
| |/
|
|
|
|
|
|
| |
For the most part, this is just code movement. The implementation was
copied over to `define_derive_adhoc` from `define_key_specifier`, with
some minor adjustments that were needed to make it compile.
Closes #1093
|
| |\
| |
| |
| |
| | |
New tor-log-ratelim crate (improved varsion)
See merge request tpo/core/arti!1734
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This crate is meant to provide rate-limited log messages
to tell users about problems that can happen too frequently
to log individually.
This version is based off an earlier design, and off of
conversations with @diziet. It still needs tests.
|
| | |
| |
| |
| |
| |
| | |
This is the approach from appendix F.2 in rend-spec.
Part of #1053.
|
| |\ \
| | |
| | |
| | |
| | | |
Upgrade a couple of dependencies
See merge request tpo/core/arti!1736
|
| | | | |
|
| | |/ |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
See comments for design notes.
|
| |
|
|
|
|
|
| |
tor-rpcbase patchlevel only, depends on async-utils.
tor-llcrypto patchlevel only, depends on basic-utils.
tor-hspow patchlevel only, depends on hscrypto.
tor-linkspec patchlevel only, depends on basic-utils
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
```
These crates have new APIs:
tor-async-utils ADDED
tor-config ADDED
tor-hscrypto ADDED
tor-netdoc ADDED, plus BREAKING-experimental.
These crates have patch-level changes only:
tor-netdir (bugfix only). (re-exposes netdoc)
arti-rpcserver (tweaks only, uses nothing that broke.)
arti 1.1.10, no stable public APIs.
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
```
tor-basic-utils BREAKING
tor-rtmock BREAKING.
tor-cert BREAKING
tor-cell BREAKING
tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental)
tor-chanmgr BREAKING: Re-exposes proto.
tor-ptmgr BREAKING: re-exposes tor-chanmgr
tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?)
tor-circmgr BREAKING: re-exposes proto
tor-dirclient BREAKING
tor-hsclient BREAKING, re-exposes proto.
tor-hsservice BREAKING, re-exposes proto.
tor-hsrproxy BREAKING
arti-client BREAKING: re-exposes proto.
arti-hyper: BREAKING, re-exposes arti-client.
tor-dirmgr Let's assume BREAKING, very high-level.
tor-keymgr BREAKING, but experimental.
```
|
| |
|
|
|
|
|
|
|
|
|
| |
Representing the supported HTYPEs as `HandshakeType`s instead of `u32`s
makes it more difficult to pass in wrong/invalid values to
`HsDescBuilder::create2_formats`.
This also fixes a descriptor publisher bug spotted by @jnewsome, where
the advertised CREATE2 HTYPEs included HTYPE `1`, which is actually
supposed to be a reserved value. The publisher now only advertises the
`NTOR` HTYPE (just like C Tor).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
`ahash 0.8.3` has been [yanked], which is causing the cargo audit
job to fail.
[yanked]: https://github.com/tkaitchuck/aHash/wiki/Yanked-versions
|
| | |
|
| | |
|
| |
|
|
|
| |
(This is only used in the disabled tor-events crate, but it's
still easier to keep dependencies up-to-date than not.)
|
| | |
|
| | |
|
| |
|
|
|
| |
This doesn't test all the code paths, but it does test the main path
of execution (and detected a couple of bugs).
|
| |
|
|
|
| |
This should be smaller and faster than vec, and save some
allocations. It could also avoid a tiny sidechannel.
|
| | |
|