<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-hscrypto/src, branch arti-v1.1.12</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.12</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-13T16:09:53Z</updated>
<entry>
<title>Merge branch 'wallclock-time' into 'main'</title>
<updated>2023-12-13T16:09:53Z</updated>
<author>
<name>gabi-250</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-12-13T16:09:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ca90f9cf017e269071b1364587c51a75ad5c5995'/>
<id>urn:sha1:ca90f9cf017e269071b1364587c51a75ad5c5995</id>
<content type='text'>
tor-hscrypto: Return 0 if the timestamp is before the start of the TP.

Closes #1155

See merge request tpo/core/arti!1828</content>
</entry>
<entry>
<title>tor-hscrypto: Return 0 if the timestamp is before the start of the TP.</title>
<updated>2023-12-13T12:09:21Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-12-13T11:56:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c853c48ea1e143bbdeb77d1b968d6f14aa62f6e1'/>
<id>urn:sha1:c853c48ea1e143bbdeb77d1b968d6f14aa62f6e1</id>
<content type='text'>
#1155 was happening because we couldn't compute the offset of the
current time from the start of the _next_ TP
(`TimePeriod::offset_within_period` expected `when` to come after the
start of the TP). `TimePeriod::offset_within_period` now returns an
offset of 0 for timestamps that come before the start of the TP, to
support computing revision counters for the descriptors uploaded to
the HsDirs from the ring associated with the next TP.

Fixes #1155
</content>
</entry>
<entry>
<title>hscrypto: Remove a "TODO HSS" about a no-longer-unused type.</title>
<updated>2023-12-12T12:41:01Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-12T12:37:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e279b3d5c70c9912d35156d0f0e996cdf6ff8c8e'/>
<id>urn:sha1:e279b3d5c70c9912d35156d0f0e996cdf6ff8c8e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>llcrypto: Hide the members of ExpandedKeypair.</title>
<updated>2023-11-29T17:10:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T17:10:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=adc3209c6bef9cc03542c31c22c0f308938e1643'/>
<id>urn:sha1:adc3209c6bef9cc03542c31c22c0f308938e1643</id>
<content type='text'>
With this change, we no longer expose the ExpandedSecretKey
unescorted, which makes it harder to misuse the API.
</content>
</entry>
<entry>
<title>llcrypto: Remove ExpandedSecretKey export.</title>
<updated>2023-11-29T16:11:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T16:11:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4470b378f69caf42dcf81277b9883247e2c62103'/>
<id>urn:sha1:4470b378f69caf42dcf81277b9883247e2c62103</id>
<content type='text'>
This type was part of `hazmat`, and was no longer necessary anywhere
in our codebase.  (It had one remaining user, which was easy enough
to remove.)  By removing it, we remove the opportunity for using an
unescorted ed25519 private key.
</content>
</entry>
<entry>
<title>Remove RngCompatExt.</title>
<updated>2023-11-29T15:55:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T15:49:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7fb24cb69da537ac04ab2dae80997c6d481622ef'/>
<id>urn:sha1:7fb24cb69da537ac04ab2dae80997c6d481622ef</id>
<content type='text'>
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.)
</content>
</entry>
<entry>
<title>Convert to the latest versions of dalek-cryptography</title>
<updated>2023-11-29T15:34:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-21T15:58:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=98037a2c788bd901679139178d25f855324637f3'/>
<id>urn:sha1:98037a2c788bd901679139178d25f855324637f3</id>
<content type='text'>
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 `&amp;[u8]` now take `&amp;[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.
</content>
</entry>
<entry>
<title>tor-hscrypto: Add a TODO re re-implementation of x25519 keypair gen</title>
<updated>2023-11-23T17:30:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-11-23T17:24:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2193268fb102ae7deebfc010f7fd1f16621dae43'/>
<id>urn:sha1:2193268fb102ae7deebfc010f7fd1f16621dae43</id>
<content type='text'>
IMO it is quite undesirable to have multiple copies of "gen a secret
key and make a keypair out of it".  Add a TODO HSS and and a ref to
arti#1137 which is related.
</content>
</entry>
<entry>
<title>tor-hscrypto: Add a docs TODO re the define_pk_keypair macro</title>
<updated>2023-11-23T17:29:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-11-23T17:12:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8f95a1cd1c3166534735704ca1115c32ebd540d5'/>
<id>urn:sha1:8f95a1cd1c3166534735704ca1115c32ebd540d5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-hscrypto: Define Keypair conversions for all curve25519 newtypes</title>
<updated>2023-11-23T17:29:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-11-23T14:54:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8406d0d76ee3ed4d82121195c806f77a45dd7de8'/>
<id>urn:sha1:8406d0d76ee3ed4d82121195c806f77a45dd7de8</id>
<content type='text'>
1. Move `impl From&lt;SpecificKeypair&gt; for curve25519::StaticKeypair`
   (which was just a bespoke impl for HsClientDescEncKeypair)
   into the define_pk_keypair macro, so everything has it.
   Currently the only other user of the curve25519_pair feature is HsSvcNtorKey.

2. Provide the reverse conversion too.
</content>
</entry>
</feed>
