<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-proto/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-02T15:04:18Z</updated>
<entry>
<title>clippy: consequential rustfmt</title>
<updated>2024-01-02T15:04:18Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-01-02T12:49:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1ba7e8a78f21b5e1c26c87d12e7a77ebb3a8949d'/>
<id>urn:sha1:1ba7e8a78f21b5e1c26c87d12e7a77ebb3a8949d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>clippy nightly: For now, locally allow blocks_in_conditions</title>
<updated>2024-01-02T15:04:18Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-01-02T14:51:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2e459400ebc4cb40622cf2eb42803afafbc05ad4'/>
<id>urn:sha1:2e459400ebc4cb40622cf2eb42803afafbc05ad4</id>
<content type='text'>
Filed
  https://gitlab.torproject.org/tpo/core/arti/-/issues/1176
proposing a final fix.
</content>
</entry>
<entry>
<title>clippy: Use infallible calls</title>
<updated>2024-01-02T13:56:22Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-01-02T12:48:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0ce386a24bd5b0490aee28345f90c7ac956a844d'/>
<id>urn:sha1:0ce386a24bd5b0490aee28345f90c7ac956a844d</id>
<content type='text'>
Resolves clippy complaints about needless fallible conversions.
</content>
</entry>
<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>Rename {Any}RelayCell to {Any}RelayMsgOuter</title>
<updated>2023-12-14T16:56:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-14T16:43:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8c0b166de3057e0ddb0d7771e50ad5a366bdd7c8'/>
<id>urn:sha1:8c0b166de3057e0ddb0d7771e50ad5a366bdd7c8</id>
<content type='text'>
This commit is pure renaming, done automatically with rust-analyzer.
Comment fixes and other cleanups will be in the subsequent commits.

We're doing this renaming because we need a name for
the combination of a `RelayMsg` and an `Option&lt;StreamId&gt;`
that we use when we have a `RelayMsg`
we intend to route to a given stream or circuit internally.
Previously we called this a `RelayCell`,
but that name was already somewhat inaccurate,
and will become _very_ inaccurate with the arrival of prop340,
which breaksthe 1:1 relationship between relay cells
and relay messages.

(If we didn't do this renaming now, we'd soon be making
the relationship between `UnparsedRelayCell`and `RelayCell`
many-to-many, which would be ridiculous and confusing.)

The `RelayMsgOuter` name is a placeholder:
We expect that we'll want to rename this type,
and may also want to rename `RelayMsg`,
and unify our vocabulary in other areas too.
But such a renaming will have to wait
for a larger discussion affecting the specifications,
so that we can use the same vocabulary everywhere.
</content>
</entry>
<entry>
<title>NtorV3Extension set encoding/decoding: include n_extensions</title>
<updated>2023-12-07T15:45:45Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2023-11-29T15:55:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cea4c505d8088f91cbe6b2884a9d54acafd80081'/>
<id>urn:sha1:cea4c505d8088f91cbe6b2884a9d54acafd80081</id>
<content type='text'>
An encoded set of extensions in the ntorv3 handshake includes a header
with the number of extensions. This change adds that header.

It also changes `write_many_onto` to take a slice instead of an
iterator, since we need to know the number of extensions up-front. In
principle we could take a clonable iterator instead and use
Iterator::count, but it's probably not worth the extra complexity.
</content>
</entry>
<entry>
<title>Merge branch 'semver-breaking-upgrade-of-the-daleks' into 'main'</title>
<updated>2023-11-29T20:51:12Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T20:51:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bdea25be86cd3e0e327d34f6748140af1c6f3b69'/>
<id>urn:sha1:bdea25be86cd3e0e327d34f6748140af1c6f3b69</id>
<content type='text'>
Convert to the latest versions of dalek-cryptography

Closes #808

See merge request tpo/core/arti!1767</content>
</entry>
<entry>
<title>debug log: Downgrade circuit lifecycle messages to trace</title>
<updated>2023-11-29T18:51:30Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-11-29T18:49:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e1b952cb964df91be6904eced2ad5120bcdc6b06'/>
<id>urn:sha1:e1b952cb964df91be6904eced2ad5120bcdc6b06</id>
<content type='text'>
This makes it possible to see the wood for the trees.

This may be controversial, but I think it's an improvement.
</content>
</entry>
<entry>
<title>Downgrade some messages to trace</title>
<updated>2023-11-29T18:51:30Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-11-29T18:44:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d67519d71b2f452dcc947acc12b3bdc50e3e7920'/>
<id>urn:sha1:d67519d71b2f452dcc947acc12b3bdc50e3e7920</id>
<content type='text'>
These messages are very verbose and I doubt anyone will want them,
usually, even when debugging.
</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>
</feed>
