<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-key-forge/semver.md, 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-24T19:11:48Z</updated>
<entry>
<title>Use an EntropicRng trait to enforce key generation rules.</title>
<updated>2025-03-24T19:11:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-20T15:09:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8a33afe155e9bd29d9302b4b44dd5843d00866db'/>
<id>urn:sha1:8a33afe155e9bd29d9302b4b44dd5843d00866db</id>
<content type='text'>
We want to require that whenever we generate a key that's persistent
(stored in KeyMgr), it's going to be made from a stronger-than-usual
Rng.  This trait helps us enforce that.

We also add a FakeEntropicRng struct to use for testing.

Note that this turned up a case that we'd missed, which required
an internal change in tor-hsservice.
</content>
</entry>
<entry>
<title>Remove semver.md files post release</title>
<updated>2025-02-07T14:33:01Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-02-07T14:33:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=534d5b7d300ec824f8776eaf0e5b434d9690f2c8'/>
<id>urn:sha1:534d5b7d300ec824f8776eaf0e5b434d9690f2c8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-key-forge: Add missing semver.md entries.</title>
<updated>2025-01-13T19:29:19Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-01-13T19:21:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b6ecf6758ea7d136340c507f45db02259c9685e2'/>
<id>urn:sha1:b6ecf6758ea7d136340c507f45db02259c9685e2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-key-forge: Split out ItemType as a separate trait.</title>
<updated>2025-01-13T19:22:36Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-12-10T20:27:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d45ab843b6506dfbfea456ed585c34f60100a280'/>
<id>urn:sha1:d45ab843b6506dfbfea456ed585c34f60100a280</id>
<content type='text'>
This is necessary because `ParsedCert`s will not be `EncodableItem`s.
This is because we cannot (and don't want to) write certificates that
have not yet been validated to the keystore. They do need to be
retrievable from the keystore though, so we also change `ErasedKey`
to be `Box&lt;dyn ItemType&gt;` instead.
</content>
</entry>
<entry>
<title>Remove semver.md files after 1.3.2 release</title>
<updated>2025-01-07T17:35:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-07T17:35:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b6f7e815065c0659c77a58052e6f7c0338b4056e'/>
<id>urn:sha1:b6f7e815065c0659c77a58052e6f7c0338b4056e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-key-forge: Abolish the HasKind impl of Error.</title>
<updated>2024-12-10T11:49:34Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-12-10T11:49:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=066fa6d4bedc0d1cc6304ff28c6a23ba18bd1f0f'/>
<id>urn:sha1:066fa6d4bedc0d1cc6304ff28c6a23ba18bd1f0f</id>
<content type='text'>
We can't possibly know the `ErrorKind` of such an error, unless we know
where the unsupported key came from. Since we can't know this, we should
let a higher level crate (like `tor-keymgr`) decide the `ErrorKind`
instead.
</content>
</entry>
</feed>
