<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-llcrypto/tests, branch arti-v1.1.2</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-01-27T13:27:47Z</updated>
<entry>
<title>Disable clippy::unlinlined-format-args</title>
<updated>2023-01-27T13:27:47Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T12:49:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bf04641c6818cb2c87c6ed9cf463a5710f8919d2'/>
<id>urn:sha1:bf04641c6818cb2c87c6ed9cf463a5710f8919d2</id>
<content type='text'>
This warning kind of snuck up on us! (See #748)  For now, let's
disable it.  (I've cleaned it up in a couple of examples, since
those are meant to be more idiomatic and user-facing.)

Closes #748.
</content>
</entry>
<entry>
<title>Complete our migration to base64ct.</title>
<updated>2023-01-20T13:06:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-19T19:50:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=889206cde4ef29d7d10bda546f8ad518eb09c290'/>
<id>urn:sha1:889206cde4ef29d7d10bda546f8ad518eb09c290</id>
<content type='text'>
This is in lieu of upgrading to the latest base64 crate, which has
a different API from the old one.  Since we have to migrate either
way, we might as well use base64ct everywhere.

I don't think that most of these cases _require_ constant-time
base64, but it won't hurt.
</content>
</entry>
<entry>
<title>Merge branch 'fix-nightly-clippy' into 'main'</title>
<updated>2022-09-22T16:45:52Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2022-09-22T16:45:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a773a753b3220dc41f61a9ac89abb5c6e1558f9e'/>
<id>urn:sha1:a773a753b3220dc41f61a9ac89abb5c6e1558f9e</id>
<content type='text'>
Fix nightly clippy

See merge request tpo/core/arti!729</content>
</entry>
<entry>
<title>Add a new constant-time is_zero() check for RsaIdentity</title>
<updated>2022-09-20T13:13:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-20T13:13:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=657914f7787a0ac5bdaad8c15d41a91425e1c8cf'/>
<id>urn:sha1:657914f7787a0ac5bdaad8c15d41a91425e1c8cf</id>
<content type='text'>
There are some places in the protocol where we have an all-zero RSA
identity that does not truly represent a key, but rather represents
an absent or unknown key.  For these, it's better to use
`RsaIdentity::is_zero` instead of manually checking for a set of
zero bytes: it expresses the intent better, and ensures that the
operation is constant-time.

I am deliberately not introducing a more general IsZero trait here,
or implementing is_zero for anything else: This is the only one we
seem to need right now.  We can generalize it later if we have to.
</content>
</entry>
<entry>
<title>fix clippy::needless_borrow</title>
<updated>2022-09-10T12:39:47Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-09-10T12:39:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8e7a904260dfe344eed70a9eef109695544347c1'/>
<id>urn:sha1:8e7a904260dfe344eed70a9eef109695544347c1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use testing_rng() in tests throughout our crates.</title>
<updated>2022-06-02T18:56:42Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-02T17:31:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=967ea67b7dfc158f29cf449eb09bac89acdee46b'/>
<id>urn:sha1:967ea67b7dfc158f29cf449eb09bac89acdee46b</id>
<content type='text'>
This only affects uses of thread_rng(), and affects them all more or
less indiscriminately.  One test does not work with
ARTI_TEST_PRNG=deterministic; the next commit will fix it.
</content>
</entry>
<entry>
<title>Upgrade to AES 0.8</title>
<updated>2022-04-26T16:16:22Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-25T19:39:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aaab6f38122261f7527e9a04b24972d09b775689'/>
<id>urn:sha1:aaab6f38122261f7527e9a04b24972d09b775689</id>
<content type='text'>
Now that we require Rust 1.56, we can upgrade to AES 0.8.  This
forces us to have some slight API changes.

We require cipher 0.4.1, not cipher 0.4.0, since 0.4.0 has
compatibility issues with Rust 1.56.
</content>
</entry>
<entry>
<title>squash! Bump every crate's edition to 2021.</title>
<updated>2022-04-25T17:06:26Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-25T16:40:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2f6bc6bdc431fa36de70a167eea777dcf3f60bf2'/>
<id>urn:sha1:2f6bc6bdc431fa36de70a167eea777dcf3f60bf2</id>
<content type='text'>
Remove all `use` statements for `TryFrom` and `TryInto`.  These are
now redundant in Rust 2021.
</content>
</entry>
<entry>
<title>Add a from_hex method for RsaIdentity.</title>
<updated>2022-03-04T13:55:34Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-04T13:55:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b6452b481215ce0963123630234b01be0c440092'/>
<id>urn:sha1:b6452b481215ce0963123630234b01be0c440092</id>
<content type='text'>
We perform this operation in a bunch of places, and most of them
use hex::decode().  That's not great, since hex::decode() has to do
heap allocation.  This implementation uses hex::decode_to_slice(),
which should be faster.

(In the future we might choose to use one of the faster hex
implementations, but I'm hoping that this change will be sufficient
to get hex decoding out of our profiles.)

Part of #377.
</content>
</entry>
<entry>
<title>tor-llcrypto: Add test case for RsaIdentity formatting</title>
<updated>2022-03-02T16:25:01Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-02T16:21:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7a4369e240948cdc27c7ad03f40a42efbc52b95b'/>
<id>urn:sha1:7a4369e240948cdc27c7ad03f40a42efbc52b95b</id>
<content type='text'>
I'm going to change the code that does this, so add a test first
to check the output doesn't change.

At some point we should have more RSA tests.
</content>
</entry>
</feed>
