<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/doc, branch arti-v1.3.2</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-01-06T20:36:37Z</updated>
<entry>
<title>fix: fix typos</title>
<updated>2025-01-06T20:36:37Z</updated>
<author>
<name>Dimitris Apostolou</name>
<email>dimitris.apostolou@icloud.com</email>
</author>
<published>2024-12-25T20:48:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4acfc23b70c51d2637d0274943a82d1c94dec050'/>
<id>urn:sha1:4acfc23b70c51d2637d0274943a82d1c94dec050</id>
<content type='text'>
</content>
</entry>
<entry>
<title>PoW: Consolidate feature flags into a single flag.</title>
<updated>2024-11-25T20:49:46Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-11-25T20:45:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7846ed242bf39d9b366f47393de28056d70abec0'/>
<id>urn:sha1:7846ed242bf39d9b366f47393de28056d70abec0</id>
<content type='text'>
This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full
features with a single hs-pow-full feature.

It's possible that in the future we will want to split different schemes
into different features, but we can do that when it comes up.

For now, having this as a single flag makes it clearer what's going on,
since the previous thing was not actually expressive enough to capture
some things we care about (like "at least one pow scheme is enabled"
that works in a future-compatible way).

This change is not semver breaking since it's a experimental feature.

Related: #1751
</content>
</entry>
<entry>
<title>tor-netdoc: Error on PowParams::V1 when hs-pow-v1 is disabled.</title>
<updated>2024-11-25T19:34:37Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-11-25T18:08:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=83b52c11e04c60b238600f159ba227f007a81dde'/>
<id>urn:sha1:83b52c11e04c60b238600f159ba227f007a81dde</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Don't include pow_params in HsDesc when feature is disabled.</title>
<updated>2024-11-25T19:34:37Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-11-21T20:40:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a0f5d61d344f289e7c0fdeaff1b6d3e16e261049'/>
<id>urn:sha1:a0f5d61d344f289e7c0fdeaff1b6d3e16e261049</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Support writing pow-params line.</title>
<updated>2024-11-25T18:20:11Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-10-15T18:39:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f740995ca2db08842f3306fda30aa57e0e67bd1c'/>
<id>urn:sha1:f740995ca2db08842f3306fda30aa57e0e67bd1c</id>
<content type='text'>
I'm not particularly happy with the code that does the actual writing
out of the pow-params line, in particular the error handling there seems
very verbose. However, I don't know of a better way to structure it
given that APIs I'm working with.
</content>
</entry>
<entry>
<title>TimerangeBound: Stop using std::ops::Bound.</title>
<updated>2024-11-25T18:20:11Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-10-15T13:58:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1659495eb30ae6a17058418b6d00592373cfdf65'/>
<id>urn:sha1:1659495eb30ae6a17058418b6d00592373cfdf65</id>
<content type='text'>
Fixes: #1691
</content>
</entry>
<entry>
<title>tor-netdoc: add clippy allows and `#[non_exhaustive]`</title>
<updated>2024-11-20T17:52:56Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-11-20T03:58:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=28b9def7584cdc6265b30cb9d0fd2a1f1e8b2d01'/>
<id>urn:sha1:28b9def7584cdc6265b30cb9d0fd2a1f1e8b2d01</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add a little test coverage for pow-params parsing.</title>
<updated>2024-10-09T16:06:01Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-10-01T18:57:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e363576b91e489941065f73b5e89d2e1128c744e'/>
<id>urn:sha1:e363576b91e489941065f73b5e89d2e1128c744e</id>
<content type='text'>
Cover some of the novel edge cases we're introducing around object
parameters and repetition. This still feels awfully ad-hoc, but it's
better than nothing.

Co-authored-by: Micah Elizabeth Scott &lt;beth@torproject.org&gt;
</content>
</entry>
<entry>
<title>hs-pow inner desc: broaden pow-params rule, disallow object for v1.</title>
<updated>2024-10-09T16:06:01Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-10-01T18:55:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0f473a1563debc89fdaef40739e49c1e40ac52eb'/>
<id>urn:sha1:0f473a1563debc89fdaef40739e49c1e40ac52eb</id>
<content type='text'>
We should not be restricting pow-params to occur only once at the rule
level, and we shouldn't be disallowing object parameters at that level
either. Instead, the v1 scheme itself needs to check for and disallow
objects. Future schemes may allow object parameters.

Test cases for this will be added in a subsequent commit.

Co-authored-by: Micah Elizabeth Scott &lt;beth@torproject.org&gt;
</content>
</entry>
<entry>
<title>hs-pow: inner doc test using canned data from C tor.</title>
<updated>2024-10-09T16:06:01Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-10-01T18:50:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=523035341a8139fe7404294ee14c99dde2456ff1'/>
<id>urn:sha1:523035341a8139fe7404294ee14c99dde2456ff1</id>
<content type='text'>
This proliferates the canned hsdesc inner doc testing strategy, adding
another file with data encoded with onion-pow-example running on C
tor. Tests that it parses successfully, and asserts that the pow params
line contents are correct. This is a positive test only.

This strategy seems problematic, but it's better than nothing.

Co-authored-by: Micah Elizabeth Scott &lt;beth@torproject.org&gt;
</content>
</entry>
</feed>
