<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-cell/src/relaycell/extend.rs, branch arti-v1.1.10</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.10</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.10'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-02-09T15:20:31Z</updated>
<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>Merge branch 'fallible_writers_v2' into 'main'</title>
<updated>2022-07-19T20:29:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-19T20:29:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f1de00369ea597b2abf09e20a7c89d628e2d63e'/>
<id>urn:sha1:6f1de00369ea597b2abf09e20a7c89d628e2d63e</id>
<content type='text'>
Revise tor_bytes::Writer::write to return a Result.

Closes #513

See merge request tpo/core/arti!623</content>
</entry>
<entry>
<title>tor-cell: Derive Eq for NtorV3Extension</title>
<updated>2022-07-18T16:49:59Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-18T16:49:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bcf94f33e0f6b0d02a5ced0a8fb8a608e7ca0ec6'/>
<id>urn:sha1:bcf94f33e0f6b0d02a5ced0a8fb8a608e7ca0ec6</id>
<content type='text'>
Apropos clippy complaint.
</content>
</entry>
<entry>
<title>Convert each write_onto_infallible implementation into write_onto.</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-08T15:37:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8810af7f6522d43408e30d04d21c4ec6102d73b3'/>
<id>urn:sha1:8810af7f6522d43408e30d04d21c4ec6102d73b3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename "write" methods on tor-bytes to "write_infallible".</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-08T15:20:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7938f65c66020d6d7f143307f3336f340f398c63'/>
<id>urn:sha1:7938f65c66020d6d7f143307f3336f340f398c63</id>
<content type='text'>
This comprises four renames:

```
write_onto -&gt; write_onto_infallible
write_into -&gt; write_into_infallible
write -&gt; write_infallible
writer_and_consume -&gt; write_and_consume_infallible.
```

The rest of this branch will be concerned with replacing these
`_infallible` methods with ones that return a `Result`.  This is
part of #513.
</content>
</entry>
<entry>
<title>Implement a higher-level API for the ntor v3 handshake</title>
<updated>2022-07-08T17:26:18Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2022-06-23T13:51:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=af64a0a984cb357c0b60cea650ca90d8d1c6240d'/>
<id>urn:sha1:af64a0a984cb357c0b60cea650ca90d8d1c6240d</id>
<content type='text'>
This implements a higher-level API for the ntor v3 handshake, in line
with that exposed by the ntor handshake. It does not, however, use the
existing `ClientHandshake` trait, due to fundamental differences in the
handshakes (namely, that the v3 handshake can include some additional
extra extension data).

Currently, the higher-level API assumes circuit extension, and copies
the (undocumented!) magic verification string from c-tor that indicates
this usage.

A rudimentary set of functions for serializing and deserializing
extensions to be sent with the handshake is also included, implementing
the protocol in proposal 332 § A.2. Currently, it only implements the
congestion control extensions specified in proposal 324 § 10.3.

part of arti#88
</content>
</entry>
</feed>
