| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Downgrade some messages to trace
See merge request tpo/core/arti!1778
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes it possible to see the wood for the trees.
This may be controversial, but I think it's an improvement.
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
These messages are very verbose and I doubt anyone will want them,
usually, even when debugging.
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
tor-hsservice tests: Introduce new test_temp_dir helper module
See merge request tpo/core/arti!1762
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
from obtain_in.
As per irc discussion.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
from UsingTempDir.
As per irc discussion.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Mandatory whitespace degradation.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We're going to want this for other tests in this crate.
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
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().
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Fix extra features getting enabled in the arti-extra test binary
See merge request tpo/core/arti!1776
|
| | | | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
We were missing `-p arti` in the build command. As a result we were
getting the union of all features requested by anything in the
workspace, including an example enabling the `experimental` feature
which enables a bunch of other things.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
tor-hsservice: time_store: Improve serialisation to be more human readable
See merge request tpo/core/arti!1774
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Suggestion 3 from
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1774#note_2970374
|
| | | |
| | |
| | |
| | |
| | | |
Suggestion 2 from
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1774#note_2970374
|
| | | |
| | |
| | |
| | | |
Apply deferred churn.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
When is_human_readable, use a Visitor to offer the data format
visit_str, which will often allow the data format to avoid consing an
actual String.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Being careful about overflow and avoiding panics is quite a palaver!
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We're going to want to do this for Reference too.
|
| | | |
| | |
| | |
| | | |
Use the string representation in binary formats.
|
| | | |
| | |
| | |
| | |
| | | |
Parse the string representation too.
We'll be using this for serde.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We're going to serialise different in binary formats.
|
| | |/
| |
| |
| | |
This will make them easier to adjust when we serialise differently.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-keymgr: Use the new fs-mistrust APIs
See merge request tpo/core/arti!1769
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
`ArtiNativeKeystore::list` now returns an error if the parent directory
of any of its keys doesn't pass the `CheckedDir::read_dir` validation.
Part of #1117
|
| | |/
| |
| |
| |
| |
| |
| | |
This updates `ArtiNativeKeystore` to use the new `remove_file` API from
arti!1759.
Part of #1117
|
| |\ \
| |/
|/|
| |
| | |
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 necessary for async-global-executor, which uses
`futures_lite::future::or`, which futures-lite does not have before
1.4.0 or thereabouts.
|
