<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-hscrypto/README.md, branch arti-v2.0.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-08-14T22:23:29Z</updated>
<entry>
<title>docs: Add notes about hs-pow-full using LGPL deps.</title>
<updated>2025-08-14T22:23:29Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-08-13T18:52:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3103a36d1df3f4172c37bab3bfbec85220fd38fb'/>
<id>urn:sha1:3103a36d1df3f4172c37bab3bfbec85220fd38fb</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>cargo: tor-hscrypto: Declare pow-* experimental</title>
<updated>2024-10-30T15:57:12Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-30T15:47:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=36a726305d93c9db37343b5755d5e82f08195c76'/>
<id>urn:sha1:36a726305d93c9db37343b5755d5e82f08195c76</id>
<content type='text'>
We need to add the experimental feature, and the corresponding
section in the README.md.
</content>
</entry>
<entry>
<title>cargo: tor-hscrypto: Move `full` earlier in README.md</title>
<updated>2024-10-30T15:57:12Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-30T15:46:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8ceab418878ab4dd79bbfa81cf515e3374ce7903'/>
<id>urn:sha1:8ceab418878ab4dd79bbfa81cf515e3374ce7903</id>
<content type='text'>
This makes space to introduce the experimental section.
</content>
</entry>
<entry>
<title>tor-hscrypto: Document Cargo features</title>
<updated>2024-10-22T13:26:43Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-16T13:34:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c9e55595898e74b77323f9826bc24295a40e0311'/>
<id>urn:sha1:c9e55595898e74b77323f9826bc24295a40e0311</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-hspow: Big refactor, dissolve this crate</title>
<updated>2024-10-09T16:04:35Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-09-30T18:50:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5d878d3cc068572d3c14e478051ecc2361ef26b4'/>
<id>urn:sha1:5d878d3cc068572d3c14e478051ecc2361ef26b4</id>
<content type='text'>
My previous strategy here was to try and centralize hspow in one crate,
writing it like a self-contained feature. That introduced friction in
the data types, prompting the use of simplistic types at the netdoc/cell
layers and full-featured types in the optional modules.

This changes tactics, dissolving the low-level parts of tor-hspow into
tor-hscrypto and the high-level parts into hsclient/hsservice. Full
featured types are used everywhere now, but the tradeoff is that
compile-time configurability is a lot more pervasive. Anything that
knows about PoW types at all needs to be fully configured out. I took
this opportunity to try a more complete set of crate features, allowing
users to configure individual PoW schemes.

Co-authored-by: Micah Elizabeth Scott &lt;beth@torproject.org&gt;
</content>
</entry>
<entry>
<title>hscrypto: write a README</title>
<updated>2023-06-13T16:15:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-13T16:15:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=44ced7dbd3441516da783f49d0455a30d1a8ba23'/>
<id>urn:sha1:44ced7dbd3441516da783f49d0455a30d1a8ba23</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Create a new tor-hscrypto crate.</title>
<updated>2023-01-06T18:03:50Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-12-29T19:17:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0203634ec50b77b1f8bbd099da6770bc744eff45'/>
<id>urn:sha1:0203634ec50b77b1f8bbd099da6770bc744eff45</id>
<content type='text'>
This module has types and operations needed in multiple places
for an onion service implementation.  There are a bunch of
TODO hs-crypto comments that we'll need to fill in.
</content>
</entry>
</feed>
