<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-cert, branch tor-llcrypto-v0.4.4</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-03-31T12:24:39Z</updated>
<entry>
<title>Bump patchlevel on crates with non-breaking changes</title>
<updated>2023-03-31T12:24:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-03-31T12:24:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76'/>
<id>urn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76</id>
<content type='text'>
For these crates, the changes are nontrivial, so we
_do_ bump the versions on which their dependent crates depend.

Fortunately, since they are all pre-1.0, we don't need to
distinguish semver-additions from other changes.  (Except for arti,
which _is_ post-1.0, but gets a patchlevel bump anyway.)

These are unstable crates with breaking changes:

```
tor-hscrypto
tor-hsclient
```

These have new or extended APIs:

```
safelog
tor-bytes
tor-cell
tor-linkspec
tor-llcrypto
tor-proto
tor-cert
arti-client
```

These have new unstable APIs or features:
```
tor-netdoc
tor-circmgr (also broke some unstable APIs)
arti (is post-1.0)
```

These have bugfixes only:
```
caret
tor-dirmgr
```
</content>
</entry>
<entry>
<title>Use the type system to enforce use of blinded keys.</title>
<updated>2023-03-27T10:45:51Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-03-22T19:09:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1d4069cc7f233c40c079a6dfbc7f5d93f350c555'/>
<id>urn:sha1:1d4069cc7f233c40c079a6dfbc7f5d93f350c555</id>
<content type='text'>
Hidden services use blinded singing keys derived from the identity key
to sign descriptor signing keys.

Before this patch, the hidden descriptor builder represented its blinded
signing keys (`blinded_id`) as plain `ed25519::Keypair`s. This was not
ideal, as there was nothing preventing the caller from accidentally
initializing `blinded_id` with an unblinded keypair.

This introduces a new `HsBlindKeypair` type to represent blinded
keypairs.

Signed-off-by: Gabriela Moldovan &lt;gabi@torproject.org&gt;
</content>
</entry>
<entry>
<title>Remove semver.md files now that 1.1.2 is out.</title>
<updated>2023-02-28T15:06:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-28T15:06:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=886faa96b3c0e42ba066ddc5de73209b10ce58da'/>
<id>urn:sha1:886faa96b3c0e42ba066ddc5de73209b10ce58da</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Patchlevel bumps for remaining changed crates.</title>
<updated>2023-02-28T12:13:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-28T12:13:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f41449d0bd9a2db5f72dd9941fb897e5cd9b922d'/>
<id>urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d</id>
<content type='text'>
These crates have had small code changes, but no API additions:

tor-config
tor-socksproto
tor-cert
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
arti
tor-hsservice
tor-congestion

These crates have had API extensions:

fs-mistrust
tor-llcrypto
tor-bytes
tor-checkable
tor-linkspec
tor-netdoc
tor-persist
arti-client
</content>
</entry>
<entry>
<title>Merge branch 'ticket_525_part2' into 'main'</title>
<updated>2023-02-09T18:06:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-09T18:06:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=696b9bd2d572b2a6b990c86a3f598c00664bf040'/>
<id>urn:sha1:696b9bd2d572b2a6b990c86a3f598c00664bf040</id>
<content type='text'>
Apply restricted_msg to ChanMsg parts of tor-proto

See merge request tpo/core/arti!1013</content>
</entry>
<entry>
<title>Change tor_bytes::Error::BadMessage to a Cow.</title>
<updated>2023-02-09T15:20:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-08T13:51:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=48ab7b0463aaada172a426ad4b20a63d7f44cb84'/>
<id>urn:sha1:48ab7b0463aaada172a426ad4b20a63d7f44cb84</id>
<content type='text'>
Actually, to avoid making a breaking change, I'm deprecating
BadMessage and creating a new InvalidMessage variant that takes a
Cow.  This way I don't need to track every crate that re-exposes
tor_bytes::Error and call this a breaking change in those.

Making this change will allow tor_bytes errors to be much more
helpful.
</content>
</entry>
<entry>
<title>Rename key identifiers that have changed in the spec</title>
<updated>2023-02-08T16:57:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-08T16:57:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=18e8ac7cb664067913c04a7091907fad785aaef1'/>
<id>urn:sha1:18e8ac7cb664067913c04a7091907fad785aaef1</id>
<content type='text'>
Generated with perl:

s/K([PS])_hs_intro_tid/K$1_hs_ipt_sid/g;
s/K([PS])_onion_ntor/K$1_ntor/g;
s/K([PS])_hs_intro_ntor/K$1_hss_ntor/g;
s/K([PS])_hs_desc_ephem/K$1_hss_desc_enc/g;
</content>
</entry>
<entry>
<title>tor-cert: document hs-related certificate types.</title>
<updated>2023-02-07T14:00:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-30T14:52:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a751eacd5b6a284186eee3de653980b15658a7cc'/>
<id>urn:sha1:a751eacd5b6a284186eee3de653980b15658a7cc</id>
<content type='text'>
Also, explain why a few of these certificates aren't actually useful
as certificates.  (This issue is also documented in torspec!110)
</content>
</entry>
<entry>
<title>tor-cert: Implement Timebound for Ed25519Cert</title>
<updated>2023-02-07T14:00:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-30T14:41:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=079002d2837fcf4320cb92d393719f48e5c835a7'/>
<id>urn:sha1:079002d2837fcf4320cb92d393719f48e5c835a7</id>
<content type='text'>
This allows us to run `is_valid_at` and friends on the certificate
itself, which we will use soon in hsdesc validity checks.
</content>
</entry>
<entry>
<title>Bump the patch version of every crate that had API additions</title>
<updated>2023-02-01T15:36:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-01T15:36:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4'/>
<id>urn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4</id>
<content type='text'>
These crates had API or behavior changes that may affect downstream
crates. Fortunately, they're all version 0.x, and don't need minor
bumps for this.
</content>
</entry>
</feed>
