<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-llcrypto/src/pk, branch arti-v1.1.5</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.5</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.5'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-05-18T15:00:43Z</updated>
<entry>
<title>llcrypto: Don't take or return "unescorted" ed25519 keys.</title>
<updated>2023-05-18T15:00:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-05-18T15:00:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dcec7ca2dc6563e5277f5e913759ab19884e2e69'/>
<id>urn:sha1:dcec7ca2dc6563e5277f5e913759ab19884e2e69</id>
<content type='text'>
Per #798, we want to make sure that we never pass around an
`ed25519::SecretKey`; only an `ed25519::Keypair` (or
`ExpandedKeypair`).  This is because, when you're computing an
ed25519 signature, you have to use the public key as one of your
inputs, and if you ever use a mismatched public key you are
vulnerable to a nonce reuse attack.

(For more info see
https://moderncrypto.org/mail-archive/curves/2020/001012.html )
</content>
</entry>
<entry>
<title>llcrypto: Add an `ed25519::ExpandedKeypair` type.</title>
<updated>2023-05-18T14:56:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-05-18T14:56:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2ffb200a77a6d9cf91f00a006e0d9b8684114708'/>
<id>urn:sha1:2ffb200a77a6d9cf91f00a006e0d9b8684114708</id>
<content type='text'>
This is like an `ed25519::Keypair`, except that instead of a
`SecretKey` it contains an `ExpandedSecretKey`.

We'll be using this to implement #798, where we impose a rule that
there must be no "unescorted" ed25519 secret keys.
</content>
</entry>
<entry>
<title>Use non-deprecated *Secret::random_from_rng.</title>
<updated>2023-05-13T20:52:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-05-13T20:52:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bfda3082d454e1ce6cbf62974b82395fff254c80'/>
<id>urn:sha1:bfda3082d454e1ce6cbf62974b82395fff254c80</id>
<content type='text'>
The `new` function is deprecated in x25519-dalek 2.0.0-rc.2
</content>
</entry>
<entry>
<title>update rsa to 0.9.x</title>
<updated>2023-05-08T15:24:23Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2023-05-08T15:24:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7d50a34a3acee6507749d0cb7cc908f72ca33667'/>
<id>urn:sha1:7d50a34a3acee6507749d0cb7cc908f72ca33667</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-llcrypto: key blinding: Use consistent terminology</title>
<updated>2023-03-28T11:47:12Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-03-28T11:32:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=def291dcb5c6b657296886e95a2b4fa3717b466a'/>
<id>urn:sha1:def291dcb5c6b657296886e95a2b4fa3717b466a</id>
<content type='text'>
Unhelpfully, the spec uses the variable name `h` and the phrase
"blinding factor" for both the unclamped and clamped value.  The
clamped value is internal to the algorithm.

In our code:

* Don't ever use the word "parameter" or variable name `param`.
  This doesn't appear in the spec anywhere.

* Use `h` for the unclamped blinding factor, and `blinding_factor` for the
  clamped blinding factor.

* Rename `blinding_factor` function to `clamp_blinding_factor`, since
  in the spec's terminology it takes an (unclamped) "blinding factor"
  and returns a (clamped) "blinding factor".

* State explicitly what thing in the spec the `h` parameters are.
</content>
</entry>
<entry>
<title>Use the type system to enforce use of blinded keys.</title>
<updated>2023-03-27T10:45:51Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-03-22T19:09:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1d4069cc7f233c40c079a6dfbc7f5d93f350c555'/>
<id>urn:sha1:1d4069cc7f233c40c079a6dfbc7f5d93f350c555</id>
<content type='text'>
Hidden services use blinded singing keys derived from the identity key
to sign descriptor signing keys.

Before this patch, the hidden descriptor builder represented its blinded
signing keys (`blinded_id`) as plain `ed25519::Keypair`s. This was not
ideal, as there was nothing preventing the caller from accidentally
initializing `blinded_id` with an unblinded keypair.

This introduces a new `HsBlindKeypair` type to represent blinded
keypairs.

Signed-off-by: Gabriela Moldovan &lt;gabi@torproject.org&gt;
</content>
</entry>
<entry>
<title>Expose a little new functionality from tor-llcrypto.</title>
<updated>2023-02-28T16:23:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-27T20:35:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d658fcfc52261ceab93e45fe03bb04fff922b0f8'/>
<id>urn:sha1:d658fcfc52261ceab93e45fe03bb04fff922b0f8</id>
<content type='text'>
Expose ED25519 signature length; make ValidatableEd25519Signature
implement Debug and Clone.
</content>
</entry>
<entry>
<title>llcrypto: Implement `Into&lt;[u8;32]&gt;` for Ed25519Identity</title>
<updated>2023-02-07T14:00:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-30T19:10:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=59b981ea5e652aa3f7c6ab128ca66525187162c2'/>
<id>urn:sha1:59b981ea5e652aa3f7c6ab128ca66525187162c2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-llcrypto: Tolerate some warnings (fmt)</title>
<updated>2023-01-20T17:29:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-20T17:29:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5c76bca69218487244663a23f1976b333a9bc6a0'/>
<id>urn:sha1:5c76bca69218487244663a23f1976b333a9bc6a0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-llcrypto: Tolerate some warnings</title>
<updated>2023-01-20T16:37:31Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-20T16:36:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bd21d232799b8c6dba638ff95e0f42d7b25226a3'/>
<id>urn:sha1:bd21d232799b8c6dba638ff95e0f42d7b25226a3</id>
<content type='text'>
Without this,
  cargo +stable clippy -p tor-netdoc --all-features
produces warnings.
</content>
</entry>
</feed>
