<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-hsservice/src/publish, branch arti-v1.7.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.7.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.7.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-08-19T13:46:54Z</updated>
<entry>
<title>hsservice: Move derive_more::From out of internal_prelude.</title>
<updated>2025-08-19T13:46:54Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-19T13:46:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6cb98ccc344768c0cff6b7136ea81c38d2f4e990'/>
<id>urn:sha1:6cb98ccc344768c0cff6b7136ea81c38d2f4e990</id>
<content type='text'>
This fixes an error from nightly. The trouble is that with nightly,
there's a now a [derive macro for From][issue].  That doesn't cause
a conflict when we `use derive_more::From`, but it _does_
cause a conflict when we import `derive_more::From` via
`use internal_prelude::*`.

So as a solution, we just import `derive_more::From` explicitly.

Closes #2124

[issue]: https://github.com/rust-lang/rust/pull/144922
</content>
</entry>
<entry>
<title>misc: cleanup now that `_report!` macros support fields</title>
<updated>2025-08-18T19:45:55Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-08-09T20:31:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2de5c18fae7be30c4ab3c3fae520c81fb3ff74ed'/>
<id>urn:sha1:2de5c18fae7be30c4ab3c3fae520c81fb3ff74ed</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'relay-reactor-placeholder' into 'main'</title>
<updated>2025-08-18T19:08:47Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2025-08-18T19:08:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a3bf2347bf0d91d08b2551bd0f3652ee8ae34744'/>
<id>urn:sha1:a3bf2347bf0d91d08b2551bd0f3652ee8ae34744</id>
<content type='text'>
proto: Add a placeholder for the relay reactor.

See merge request tpo/core/arti!3162</content>
</entry>
<entry>
<title>proto: Move the `stream` module under `client` (breaking).</title>
<updated>2025-08-18T16:09:04Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-08-18T15:52:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=702e7276898d3f31e22033c5b64fea91703f3701'/>
<id>urn:sha1:702e7276898d3f31e22033c5b64fea91703f3701</id>
<content type='text'>
The `stream` module is client-specific, for the most part, so I am
moving it under `client`. Later on, we will factor out the parts that
can be shared with the relay implementation.

Note: this is a breaking change as the deleted `stream` module was
`pub`. We could've kept the module and reexported from it the public
types from `tor_proto::client::stream`, but I think it's better to have
this `client` namespacing, because it makes the separation between the
client and relay parts clearer.
</content>
</entry>
<entry>
<title>tor-hsservice: Pass Rng into PoW code where possible.</title>
<updated>2025-08-13T18:30:37Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-08-04T19:26:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9795358e42b1de9e1f0bd54195da279ba14a29df'/>
<id>urn:sha1:9795358e42b1de9e1f0bd54195da279ba14a29df</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-hsservice: Implement enable_pow option.</title>
<updated>2025-08-13T18:30:34Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-07-29T15:33:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ba0c417801d1f50e51f9f1198776ea79f852b20f'/>
<id>urn:sha1:ba0c417801d1f50e51f9f1198776ea79f852b20f</id>
<content type='text'>
This does not currently allow this option to be changed at runtime,
although the code is structured so that allowing it to be changed at
runtime won't be too hard. This is tracked by #2082.
</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>hs: Use the new Tunnel interface for onion service</title>
<updated>2025-08-05T18:23:02Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2025-05-07T18:10:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8333a2d7c9e4842753e65d978087e54a8ad43789'/>
<id>urn:sha1:8333a2d7c9e4842753e65d978087e54a8ad43789</id>
<content type='text'>
</content>
</entry>
<entry>
<title>netdoc, hsservice: Respect maximum descriptor sizes</title>
<updated>2025-07-10T13:41:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-06-24T15:44:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1df1014e9d52ae1c848f97daadfac4d7e1c61d36'/>
<id>urn:sha1:1df1014e9d52ae1c848f97daadfac4d7e1c61d36</id>
<content type='text'>
It would be better to take a more sophisticated approach;
see #2048.
</content>
</entry>
<entry>
<title>hs*: Define some HsDesc errors as _suspicious_.</title>
<updated>2025-07-10T13:41:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-06-23T18:35:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6ff683b2cf209ff0598efcdae7947ed6a8fbebbe'/>
<id>urn:sha1:6ff683b2cf209ff0598efcdae7947ed6a8fbebbe</id>
<content type='text'>
These errors are suspicious as hsdir inflation attacks, in the
context of prop360.
</content>
</entry>
</feed>
