<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-hscrypto, branch arti-v1.1.11</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.11</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-04T16:35:23Z</updated>
<entry>
<title>Bump minor versions in preparation for release</title>
<updated>2023-12-04T16:35:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fba95e4b4708929ed09554632acd2e9f15e3c086'/>
<id>urn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086</id>
<content type='text'>
This crate is new, and gets a bump to 0.1.0.

tor-log-ratelim

This crate had a breaking change:

tor-persist

tor-llcrypto had a breaking change.  These crates _are_
tor-llcrypto, or (transitively) depend on it. I am assuming that
they all re-expose something from it in a way that matters:

tor-llcrypto
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-hyper
</content>
</entry>
<entry>
<title>Bump patchlevel versions in preparation for release</title>
<updated>2023-12-04T16:33:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=606905bd1fa3307a77a02463fa863f4c2b7cb890'/>
<id>urn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890</id>
<content type='text'>
These crates had backward-compatible changes, and get a patchlevel
bump only:

fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock

This crate exposes no non-CLI APIs, and gets a patchlevel bump only:

arti
</content>
</entry>
<entry>
<title>Merge branch 'msrv-bump-1.70' into 'main'</title>
<updated>2023-11-30T14:40:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2023-11-30T14:40:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7b23daffb5c2e903881c9b2d64a0bccc7b3f698e'/>
<id>urn:sha1:7b23daffb5c2e903881c9b2d64a0bccc7b3f698e</id>
<content type='text'>
Increase our MSRV to 1.70

See merge request tpo/core/arti!1773</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>In every crate, change rust-version to 1.70.</title>
<updated>2023-11-28T16:35:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-28T16:35:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1'/>
<id>urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1</id>
<content type='text'>
</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>
</feed>
