<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/err.rs, branch arti-v1.8.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.8.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-07-10T14:43:37Z</updated>
<entry>
<title>Merge branch 'prop360-combined' into 'main'</title>
<updated>2025-07-10T14:43:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-07-10T14:43:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=49f81a14090ae29eb944854d49a59a7125d6ee83'/>
<id>urn:sha1:49f81a14090ae29eb944854d49a59a7125d6ee83</id>
<content type='text'>
Implement proposal 360 (limit HsDesc inflation opportunities)

Closes #2046

See merge request tpo/core/arti!3070</content>
</entry>
<entry>
<title>netdoc: disallow extraneous space within final signature item</title>
<updated>2025-07-10T13:41:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-06-18T14:03:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3f088d8580833695ced0d61deedef75f82b53942'/>
<id>urn:sha1:3f088d8580833695ced0d61deedef75f82b53942</id>
<content type='text'>
Part of proposal 360.
</content>
</entry>
<entry>
<title>Typo fixes (automatic and hand-verified)</title>
<updated>2025-07-09T16:27:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-07-09T16:27:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fd24caa9959a4e9a04ad10cc047975b8566a884b'/>
<id>urn:sha1:fd24caa9959a4e9a04ad10cc047975b8566a884b</id>
<content type='text'>
Made with https://crates.io/crates/typos-cli
</content>
</entry>
<entry>
<title>netdoc: Reject BOMs and NULs.</title>
<updated>2025-03-17T17:23:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-17T17:23:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e36b7e84c795fa5fadfd40c93af8df4beac6fad7'/>
<id>urn:sha1:e36b7e84c795fa5fadfd40c93af8df4beac6fad7</id>
<content type='text'>
Per &lt;https://spec.torproject.org/dir-spec/netdoc.html&gt;,
our netdocs never have a BOM, and never have internal NULs.
This makes Arti reject such documents.

For arguments on why it's okay to increase parser strictness,
see the (forthcoming) proposal 356 at torspec!342,
and see older discussion at torspec#296.

Closes #1739.
</content>
</entry>
<entry>
<title>Upgrade to derive_more version 1.0.0</title>
<updated>2024-09-25T14:37:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:37:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6a12c2ba8515226a772d5f4a81930bf42d67535a'/>
<id>urn:sha1:6a12c2ba8515226a772d5f4a81930bf42d67535a</id>
<content type='text'>
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
</content>
</entry>
<entry>
<title>Resolve warnings about ambiguous/redundant doc links</title>
<updated>2023-08-22T13:00:33Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-22T13:00:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=80c921c6377a651ae6d6d5f65fb55f4884220416'/>
<id>urn:sha1:80c921c6377a651ae6d6d5f65fb55f4884220416</id>
<content type='text'>
Nightly rustdoc now warns if you have a link that isn't necessary,
and if you have a link that might refer to two different things.
</content>
</entry>
<entry>
<title>Fix typos</title>
<updated>2023-07-22T07:10:34Z</updated>
<author>
<name>Dimitris Apostolou</name>
<email>dimitris.apostolou@icloud.com</email>
</author>
<published>2023-07-22T07:10:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=947ddfff0cfac3fef0e3d7ebc14182c638a1d90b'/>
<id>urn:sha1:947ddfff0cfac3fef0e3d7ebc14182c638a1d90b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Test hsdescs inners with a variety of IPT counts</title>
<updated>2023-06-28T15:28:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-06-28T14:38:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=de63a6092d1abca55da65f1c157d1d8aa628d5d0'/>
<id>urn:sha1:de63a6092d1abca55da65f1c157d1d8aa628d5d0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Reject hsdescs with no intro points</title>
<updated>2023-06-28T15:27:05Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-06-28T14:09:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0e2f804d8f9f427bc111df3760339bbba4dd62ad'/>
<id>urn:sha1:0e2f804d8f9f427bc111df3760339bbba4dd62ad</id>
<content type='text'>
None of the existing NetdocErrorKinds seemed right.
</content>
</entry>
<entry>
<title>netdoc: Introduce HsDescError</title>
<updated>2023-06-22T16:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-22T16:43:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dbd255217840573ad1536e1f3ba12de1ee2229bc'/>
<id>urn:sha1:dbd255217840573ad1536e1f3ba12de1ee2229bc</id>
<content type='text'>
For higher-level HsDesc-related functions, this type indicates where
exactly an error occurred.  It lets us distinguish decryption errors
from parsing errors, and attribute responsibility to the hsdir, the
onion service, or the user's lack of encryption.

This lets us remove some just-introduced complexity in
tor-hsclient.
</content>
</entry>
</feed>
