<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/doc, branch arti-v1.4.2</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-03-18T16:09:44Z</updated>
<entry>
<title>squash! Upgrade rand dependency to 0.9.</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T14:47:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=895bc807f106e359d35522a3ad5f288ba6cf6a9c'/>
<id>urn:sha1:895bc807f106e359d35522a3ad5f288ba6cf6a9c</id>
<content type='text'>
- The Rng::gen() functions have been renamed to Rng::random().
</content>
</entry>
<entry>
<title>squash! Upgrade rand dependency to 0.9.</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T13:01:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2f8993c22c2b86010e4fd8b5169ef0ab83f8c754'/>
<id>urn:sha1:2f8993c22c2b86010e4fd8b5169ef0ab83f8c754</id>
<content type='text'>
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
</content>
</entry>
<entry>
<title>Always use full path to rand::thread_rng().</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T13:00:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=30f27c7f8f8028f833ea7e84a034f2416afd447b'/>
<id>urn:sha1:30f27c7f8f8028f833ea7e84a034f2416afd447b</id>
<content type='text'>
This is partly for consistency, and partly to facilitate
a global search-and-replace.
</content>
</entry>
<entry>
<title>Merge branch 'interface-abstraction-of-the-daleks' into 'main'</title>
<updated>2025-03-18T16:09:13Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T16:09:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=744dbdb942571399b1be7de04c9e6eea44c6b300'/>
<id>urn:sha1:744dbdb942571399b1be7de04c9e6eea44c6b300</id>
<content type='text'>
Wrap x25519-dalek and ed25519-dalek types.

See merge request tpo/core/arti!2868</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>netdoc: Make some parsing init functions fallible.</title>
<updated>2025-03-17T16:55:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-17T16:55:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f85cc0c663518edbe1c09ae2c6928e6f52cae7bb'/>
<id>urn:sha1:f85cc0c663518edbe1c09ae2c6928e6f52cae7bb</id>
<content type='text'>
I'm about to make our parsers reject some strings at construction
time, so it makes sense to have these functions become fallible.

This is a breaking change.
</content>
</entry>
<entry>
<title>netdoc: Add "family-cert" entries to routerdesc parser</title>
<updated>2025-02-25T14:29:50Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-02-10T19:04:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0a52c1690fc2cd8379e43dfcac823111df54f929'/>
<id>urn:sha1:0a52c1690fc2cd8379e43dfcac823111df54f929</id>
<content type='text'>
</content>
</entry>
<entry>
<title>netdoc: Add "family-ids" line to microdesc parser</title>
<updated>2025-02-12T16:12:13Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-02-10T19:04:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2090646f20d28152292cdfaa48d10706b4b2cc09'/>
<id>urn:sha1:2090646f20d28152292cdfaa48d10706b4b2cc09</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix: fix typos</title>
<updated>2025-01-06T20:36:37Z</updated>
<author>
<name>Dimitris Apostolou</name>
<email>dimitris.apostolou@icloud.com</email>
</author>
<published>2024-12-25T20:48:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4acfc23b70c51d2637d0274943a82d1c94dec050'/>
<id>urn:sha1:4acfc23b70c51d2637d0274943a82d1c94dec050</id>
<content type='text'>
</content>
</entry>
<entry>
<title>PoW: Consolidate feature flags into a single flag.</title>
<updated>2024-11-25T20:49:46Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-11-25T20:45:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7846ed242bf39d9b366f47393de28056d70abec0'/>
<id>urn:sha1:7846ed242bf39d9b366f47393de28056d70abec0</id>
<content type='text'>
This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full
features with a single hs-pow-full feature.

It's possible that in the future we will want to split different schemes
into different features, but we can do that when it comes up.

For now, having this as a single flag makes it clearer what's going on,
since the previous thing was not actually expressive enough to capture
some things we care about (like "at least one pow scheme is enabled"
that works in a future-compatible way).

This change is not semver breaking since it's a experimental feature.

Related: #1751
</content>
</entry>
</feed>
