<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-llcrypto/src/pk/ed25519.rs, branch arti-v1.6.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-09-23T09:43:02Z</updated>
<entry>
<title>tor-llcrypto: unconditionally use derive_deftly</title>
<updated>2025-09-23T09:43:02Z</updated>
<author>
<name>hashcatHitman</name>
<email>3924-hashcatHitman@gitlab.torproject.org</email>
</author>
<published>2025-09-23T09:43:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=71bd6f23bf2c48352fccb469439722034a593e1b'/>
<id>urn:sha1:71bd6f23bf2c48352fccb469439722034a593e1b</id>
<content type='text'>
I didn't even realize I was still conditionally using it on a feature.
That's what I get for always testing with all-features.

Signed-off-by: hashcatHitman &lt;3924-hashcatHitman@gitlab.torproject.org&gt;
</content>
</entry>
<entry>
<title>tor-(hs|ll)crypto: deftly derive ConstantTimeEq</title>
<updated>2025-09-23T08:25:49Z</updated>
<author>
<name>hashcatHitman</name>
<email>3924-hashcatHitman@gitlab.torproject.org</email>
</author>
<published>2025-09-23T08:25:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bc3de195b4f90f6bcd6697c7655a0663ceec5ef4'/>
<id>urn:sha1:bc3de195b4f90f6bcd6697c7655a0663ceec5ef4</id>
<content type='text'>
This is my initial attempt at deriving ConstantTimeEq and PartialEq.
This includes the previously missed HsSvcNtorKeypair and
HsClientDescEncKeypair types.

In tor-llcrypto, a few implementations still had to be done by hand, and
some types which previously derived normal PartialEq now derive it with
ConstantTimeEq.

I could not figure out how to properly set up the macros such that they
could be used both in the current crate and in others, so for the moment
they are duplicated. Just so I can get feedback. Ideally, this will be
replaced with a better solution before merge.

Signed-off-by: hashcatHitman &lt;3924-hashcatHitman@gitlab.torproject.org&gt;
</content>
</entry>
<entry>
<title>tor-llcrypto: fix typo</title>
<updated>2025-07-23T15:31:55Z</updated>
<author>
<name>tcyrus</name>
<email>4027-tcyrus@gitlab.torproject.org</email>
</author>
<published>2025-06-28T19:45:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=de0cf8a4eec3adda41078217d807e348664afeec'/>
<id>urn:sha1:de0cf8a4eec3adda41078217d807e348664afeec</id>
<content type='text'>
`tor_llcrypto::pk::ed25519::PublicKey` is based on `ed25519_dalek::VerifyingKey`
and not `ed25519_dalek::SigningKey`.
</content>
</entry>
<entry>
<title>llcrypto: add an rng compatibility shim for dalek-crypto</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T13:24:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9e4de6cbfe5cef6076b89f7a94a5232d47b980dd'/>
<id>urn:sha1:9e4de6cbfe5cef6076b89f7a94a5232d47b980dd</id>
<content type='text'>
dalek-cryptography is still on rand 0.8, so we need a compatibility
shim for the Rng.

Fortunately, since we merged interface-abstraction-of-the-daleks
(!2868), we no longer need to propagate this compatibility layer
throughout our codebase.
</content>
</entry>
<entry>
<title>Wrap ed25519-dalek types.</title>
<updated>2025-03-18T12:45:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-17T18:31:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d50e945a5286d89d75892878ff3aa9ed7ebed1f7'/>
<id>urn:sha1:d50e945a5286d89d75892878ff3aa9ed7ebed1f7</id>
<content type='text'>
With this change, we'll no longer need to expose the types from
dalek-cryptography as part of our API, and we'll have more freedom
to switch ed25519 implementations, or to upgrade to a newer
`rand` ahead of their schedule.

Unlike with x25519-dalek, I had to tweak the API a bit: There's no
way to get a &amp;PublicKey out of a Keypair now, and implementing the
old ed25519-dalek traits seemed unnecessary.
</content>
</entry>
<entry>
<title>Rename "memquota" feature to "memquota-memcost" when it's just HasMemoryCost (fmt)</title>
<updated>2024-10-16T13:48:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-16T13:48:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a8b2d247f35c0c5b014b6011caee2832c5f39d31'/>
<id>urn:sha1:a8b2d247f35c0c5b014b6011caee2832c5f39d31</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename "memquota" feature to "memquota-memcost" when it's just HasMemoryCost</title>
<updated>2024-10-16T13:48:11Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-16T13:43:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6ee75b3866e374250a760822b4aab49aef70e930'/>
<id>urn:sha1:6ee75b3866e374250a760822b4aab49aef70e930</id>
<content type='text'>
It's not documented anywhere ATM.  I will do that in a followup MR.
</content>
</entry>
<entry>
<title>Some HasMemoryCost impls in tor-llcrypto</title>
<updated>2024-10-02T18:11:26Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-26T20:19:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b99b6104923dc97d514fab0a7b60e9e98a3ba647'/>
<id>urn:sha1:b99b6104923dc97d514fab0a7b60e9e98a3ba647</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor_hsservice: add `impl From&lt;&amp;FooPublicKeySpecifier&gt; for FooKeypairSpecifier` instances</title>
<updated>2024-09-09T16:08:10Z</updated>
<author>
<name>Adam Joseph F0B74D717CDE8412A3E0D4D5F29AC8080DA8E1E0</name>
<email>3587-amjoseph@gitlab.torproject.org</email>
</author>
<published>2024-09-07T07:24:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2c60baee2ca6aa6c76f19d150c77d119f0d6ece4'/>
<id>urn:sha1:2c60baee2ca6aa6c76f19d150c77d119f0d6ece4</id>
<content type='text'>
This adds the following trivial `From` instances:

- tor_hsservice: impl From&lt;&amp;HsIdPublicKeySpecifier&gt; for HsIdKeypairSpecifier
- tor_hsservice: impl From&lt;&amp;BlindIdPublicKeySpecifier&gt; for BlindIdKeypairSpecifier
- tor_hscrypto::pk: impl From&lt;HsBlindIdKeypair&gt; for HsBlindIdKey
- tor_llcrypto::pk::ed25519: impl From&lt;ExpandedKeypair&gt; for PublicKey
- tor_keymgr::mgr: impl From&lt;TestKey&gt; for TestPublicKey
- tor::hscrypto::pk: impl From&lt;HsIdKeypair&gt; for HsIdKey
</content>
</entry>
<entry>
<title>Resolve an unfinished sentence</title>
<updated>2023-11-29T20:24:00Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T20:24:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5a8171683d4718b9a25e4b2a224fe1ad96f5708b'/>
<id>urn:sha1:5a8171683d4718b9a25e4b2a224fe1ad96f5708b</id>
<content type='text'>
</content>
</entry>
</feed>
