<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/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>2024-01-02T13:56:08Z</updated>
<entry>
<title>clippy: Replace many calls to .get(0) with .first()</title>
<updated>2024-01-02T13:56:08Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-01-02T12:48:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b9da8cf60618b16c021d3ecf1ec24e2dce56aff5'/>
<id>urn:sha1:b9da8cf60618b16c021d3ecf1ec24e2dce56aff5</id>
<content type='text'>
FTR I don't think agree with clippy on this question, but then I often
don't.
</content>
</entry>
<entry>
<title>tor-netdoc: Make HsDescBuilder::auth_clients take an Option.</title>
<updated>2023-12-14T18:00:17Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-12-14T17:14:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f12dd6bb65900a5bbb3540eb85b67a2c6faea949'/>
<id>urn:sha1:f12dd6bb65900a5bbb3540eb85b67a2c6faea949</id>
<content type='text'>
Closes #1019
</content>
</entry>
<entry>
<title>netdoc: Remove an "unknown_lints" exception.</title>
<updated>2023-11-30T15:16:10Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-30T14:02:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6954e1184078486f148f7d0a2cb00583d12cdc54'/>
<id>urn:sha1:6954e1184078486f148f7d0a2cb00583d12cdc54</id>
<content type='text'>
</content>
</entry>
<entry>
<title>netdoc: refactor to use a let-else.</title>
<updated>2023-11-30T15:16:10Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-30T13:58:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1bd7ea757266b5ab066dbe571454a9e2583cb7cb'/>
<id>urn:sha1:1bd7ea757266b5ab066dbe571454a9e2583cb7cb</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 redundant re-exports in keymanip.</title>
<updated>2023-11-29T16:17:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T16:17:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=af75131bcfca2c89d200fa13704be1f49a9fd94d'/>
<id>urn:sha1:af75131bcfca2c89d200fa13704be1f49a9fd94d</id>
<content type='text'>
(These types were all already re-exported from pk::ed25519.)
</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-netdoc: Use the new HandshakeType enum to represent CREATE2 HTYPEs (fmt).</title>
<updated>2023-10-30T14:18:50Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-10-30T14:18:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b5a22f3ab554329561c58b691d33a5fc3de0d5ad'/>
<id>urn:sha1:b5a22f3ab554329561c58b691d33a5fc3de0d5ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Use the new HandshakeType enum to represent CREATE2 HTYPEs.</title>
<updated>2023-10-30T14:18:02Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-10-30T13:56:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=28a0b24db240cc24230c80732c5f4ba3a0b0d461'/>
<id>urn:sha1:28a0b24db240cc24230c80732c5f4ba3a0b0d461</id>
<content type='text'>
Representing the supported HTYPEs as `HandshakeType`s instead of `u32`s
makes it more difficult to pass in wrong/invalid values to
`HsDescBuilder::create2_formats`.

This also fixes a descriptor publisher bug spotted by @jnewsome, where
the advertised CREATE2 HTYPEs included HTYPE `1`, which is actually
supposed to be a reserved value. The publisher now only advertises the
`NTOR` HTYPE (just like C Tor).
</content>
</entry>
</feed>
