<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-cell/tests, branch arti-v1.4.5</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.5</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.5'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-05-01T01:51:55Z</updated>
<entry>
<title>tor-cell: add some testing for `UnparsedRelayMsg`</title>
<updated>2025-05-01T01:51:55Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-04-30T17:49:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d9826e0722e4feb6fa6f453b8910588a2dcd896e'/>
<id>urn:sha1:d9826e0722e4feb6fa6f453b8910588a2dcd896e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cell, proto: Use correct Data sizes for v1 relay cells</title>
<updated>2025-04-16T14:58:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-04-11T01:57:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=497e5f1acd27c2c316c3f5bbf7158c9516fef159'/>
<id>urn:sha1:497e5f1acd27c2c316c3f5bbf7158c9516fef159</id>
<content type='text'>
Since v1 cells have a longer tag, they can fit less data into a
single cell.  Ah well, that's the cost of improved security.

The code in data.rs is a little wonky, in that it currently requires
its buffer to be exactly the maximum size for a data cell.  We have
a TODO about fixing that in the future, but for now I've moved it to
use a boxed slice rather than a boxed array.

Part of #1944.
</content>
</entry>
<entry>
<title>cell: Implement parsing and encoding for V1 relay cells</title>
<updated>2025-04-16T14:58:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-04-10T00:09:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=51b2102671e7ef00423299b4c6418c0bc609ec5e'/>
<id>urn:sha1:51b2102671e7ef00423299b4c6418c0bc609ec5e</id>
<content type='text'>
This is the main part of #1944, and will be needed for CGO.
</content>
</entry>
<entry>
<title>Add a RelayCellFormat argument to encode().</title>
<updated>2025-04-16T14:58:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-04-09T17:33:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=18d314e9985562a9548044920eaf0caf4935788a'/>
<id>urn:sha1:18d314e9985562a9548044920eaf0caf4935788a</id>
<content type='text'>
This will let us actually _send_ messages in the right format.

This approach is not ideal for packed/fragmented messages;
they will need a separate RelayCellEncoder.

part of #1944.
</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:34:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e3d1bbdd59638d65f872c757440010d150e0118a'/>
<id>urn:sha1:e3d1bbdd59638d65f872c757440010d150e0118a</id>
<content type='text'>
- `try_fill_bytes()` is no longer a member of RngCore.
</content>
</entry>
<entry>
<title>tor-cell: Support encoding proofs-of-work in intro_payload</title>
<updated>2024-10-09T16:04:35Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-09-26T18:06:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0a17f58f38d1b889ff9ae881d010ed7a8116bbf2'/>
<id>urn:sha1:0a17f58f38d1b889ff9ae881d010ed7a8116bbf2</id>
<content type='text'>
Like parameters, PoW solutions are versioned to account for multiple
algorithms over time. A single solution of a specific version may
accompany an INTRO1/2 as part of the encrypted extensions section. Its
encoding may depend on the version.

Co-authored-by: Micah Elizabeth Scott &lt;beth@torproject.org&gt;
</content>
</entry>
<entry>
<title>tor_bytes: Rename new_truncated_for_test to new_incomplete_for_test</title>
<updated>2024-09-12T11:48:38Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T15:51:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5314741adecad01014a069c4f0ed5018e0f6c207'/>
<id>urn:sha1:5314741adecad01014a069c4f0ed5018e0f6c207</id>
<content type='text'>
No semver implications since this wasn't in the last release.
</content>
</entry>
<entry>
<title>tor-bytes: Only report Truncated for errors at the outer level</title>
<updated>2024-09-11T13:19:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T13:13:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1632c48a5a2f5744970b841628261d6062881dee'/>
<id>urn:sha1:1632c48a5a2f5744970b841628261d6062881dee</id>
<content type='text'>
This is item 1 from
  https://gitlab.torproject.org/tpo/core/arti/-/issues/1614#note_3074562
and the alternative to item 2 presented in the 2nd half of
  https://gitlab.torproject.org/tpo/core/arti/-/issues/1614#note_3074648

(Item 3 was done earlier, but now we change the behaviour.)

Fixes #1614.
</content>
</entry>
<entry>
<title>tor-bytes: Add a Reader constructor for use in tests</title>
<updated>2024-09-11T13:19:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T12:04:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=98e563764b428e4f1aa87dc34e5fa6b5cf296938'/>
<id>urn:sha1:98e563764b428e4f1aa87dc34e5fa6b5cf296938</id>
<content type='text'>
We could call from_possibly_incomplete_slice in these, but that's
confusing and distracting.

Here we add this constructor, and document it (in terms of the
constructor to come), and change the call sites.

No functional change.  Doing this now will prevent unwanted changes to
test behaviours when we change the behaviour of Readers made by
Reader::from_slice.
</content>
</entry>
<entry>
<title>Introduce and use tor_bytes::Error::new_truncated_for_test (fmt)</title>
<updated>2024-09-10T09:10:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-05T16:03:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6b6d1d2a6c553e6275d391d6cdc6ad2dd404e83a'/>
<id>urn:sha1:6b6d1d2a6c553e6275d391d6cdc6ad2dd404e83a</id>
<content type='text'>
</content>
</entry>
</feed>
