<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-cell/tests, branch arti-v1.6.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-08-21T15:59:37Z</updated>
<entry>
<title>proto: Remove the AUTHORIZE as a parsable cell</title>
<updated>2025-08-21T15:59:37Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2025-08-21T14:52:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=eabd0c0bfe703337e338403949721ce57c87f32e'/>
<id>urn:sha1:eabd0c0bfe703337e338403949721ce57c87f32e</id>
<content type='text'>
The AUTHORIZE cell command is simply reserved but not defined. The tor
specification, at this point in time, is allowing such cell before the
handshake starts but it is very unclear on what ordering is allowed nor
how many can are allowed.

C-tor silents drop them like VPADDING and so clearly unused. Instead of
dealing with it, simply remove its support but keeping its reserved
number.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>Switch Cargo.toml files to edition 2024.</title>
<updated>2025-08-07T15:28:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:19:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=77b0de43b8c67cdb81befe0680a3df43b6ad37bc'/>
<id>urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc</id>
<content type='text'>
First, run

```
git grep -l "^edition =" |
    xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```

Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.

Third, run cargo fmt again.
</content>
</entry>
<entry>
<title>tor-cell: change `UnparsedRelayMsg::data_len`</title>
<updated>2025-07-15T06:04:44Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-15T03:50:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d499af464198520e0b4115d624b1cf53929d0024'/>
<id>urn:sha1:d499af464198520e0b4115d624b1cf53929d0024</id>
<content type='text'>
It now performs some validation and can return a `Result`.

We perform validation here since different cell formats may have
different maximum data lengths in the future, and `UnparsedRelayMsg`
doesn't expose the cell format so it's difficult to perform this
validation at a higher layer.
</content>
</entry>
<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>
</feed>
