<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-hsservice/src/svc.rs, branch ios-sqlite-hacks</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-09-18T10:53:51Z</updated>
<entry>
<title>tor-hsservice: Unify ids as IptLocalId replacing IntroPointId</title>
<updated>2023-09-18T10:53:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-09-18T10:42:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6a1bd5b2be447e96c33f4b3cb4d877ec085ab205'/>
<id>urn:sha1:6a1bd5b2be447e96c33f4b3cb4d877ec085ab205</id>
<content type='text'>
IntroPointId was RelayIds but that's wrong, because there can be
different IPTs at the same relay - but also because an established IPT
might change its RelayIds.

Use IptLocalId instead, which I think is the type we decided to use
for this, and which is, conveniently, Copy.

And change the variable names to match, everywhere.

Specifically: in places where an intro point is implied (ipt_mgr.rs,
ipt_establish.rs) use the name `lid` everywhere, like in ipt_mgr.rs.
Elsewhere, use `ipt_lid`.

(We could use a longer name, but in that case it should be changed in
ipt_mgr.rs too.)

No actual functional change in this commit.
</content>
</entry>
<entry>
<title>tor-hsservice: Have Establisher provide more information to Manager</title>
<updated>2023-08-29T16:53:32Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-29T13:40:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4c3e71ec870bcff0da8458708569b8190099f28c'/>
<id>urn:sha1:4c3e71ec870bcff0da8458708569b8190099f28c</id>
<content type='text'>
The establisher has a netdir; the manager generally doesn't.  So it
will be convenient for the establisher to provide the linkspecs and so
on.
</content>
</entry>
<entry>
<title>tor-hsservice: Make wait_for_netdir* more widely available.</title>
<updated>2023-08-25T16:53:58Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-08-23T00:05:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2ced596f1c446cc4af2632d4e0c7ff9e6d7b2f09'/>
<id>urn:sha1:2ced596f1c446cc4af2632d4e0c7ff9e6d7b2f09</id>
<content type='text'>
`wait_for_netdir` is needed by the descriptor publisher (to compute the
initial netdir).
</content>
</entry>
<entry>
<title>tor-hsservice: Expose the ipt_establish and publish modules</title>
<updated>2023-08-23T09:04:31Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-15T17:53:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b39b92b856a23951120a93e1161a6494b99495ae'/>
<id>urn:sha1:b39b92b856a23951120a93e1161a6494b99495ae</id>
<content type='text'>
I still think putting these in svc/ module doesn't make much sense.
Anyway, we can leave them there for now, but I need to get at them
from crate::ipt_establisher.
</content>
</entry>
<entry>
<title>Use "typos-cli" to fix a bunch of typos.</title>
<updated>2023-08-22T20:23:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-22T13:06:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7a37641aeb03623a707bd7f3910231c997d66bc9'/>
<id>urn:sha1:7a37641aeb03623a707bd7f3910231c997d66bc9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>HSS: Refactor RendRequest so we can return a stream of it.</title>
<updated>2023-08-22T14:50:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-18T17:06:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ec6721ec9412fa08a47855965c6a1e0ceb6e63fe'/>
<id>urn:sha1:ec6721ec9412fa08a47855965c6a1e0ceb6e63fe</id>
<content type='text'>
We need a type that holds a rend_handshake::IntroRequest object
internally, but where we don't materialize that object from the
Introduce2 message inside the MsgHandler, since that's more crypto
than we want to put in that task.
</content>
</entry>
<entry>
<title>Merge branch 'hss-err' into 'main'</title>
<updated>2023-08-18T13:39:20Z</updated>
<author>
<name>gabi-250</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-08-18T13:39:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=15f9da4d0ea60092aa1e231816e7dd69df10ba0f'/>
<id>urn:sha1:15f9da4d0ea60092aa1e231816e7dd69df10ba0f</id>
<content type='text'>
tor-hsservice errors: Introduce more error types

See merge request tpo/core/arti!1515</content>
</entry>
<entry>
<title>tor-hsservice errors: Distinguish operational errors by context</title>
<updated>2023-08-17T12:28:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-17T12:04:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=360c90a9d8ec14c713560bc089f9706527056d31'/>
<id>urn:sha1:360c90a9d8ec14c713560bc089f9706527056d31</id>
<content type='text'>
At the very least, I need FatalError to be distinct:
IptEstablisher::new ought not to fail unless everything is terrible.

Add a the Spawn variant to FatalError (that we'll need soon) and the
Bug variant (which it seems likely we might need).

This also gets rid of the crate-level Result alias.
</content>
</entry>
<entry>
<title>tor-hsservice errors: Return ReconfigureError from reconfigure</title>
<updated>2023-08-17T12:28:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-17T12:01:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e1405cdb1191de87bd771c7644233e11c1a668a8'/>
<id>urn:sha1:e1405cdb1191de87bd771c7644233e11c1a668a8</id>
<content type='text'>
This is what we do elsewhere.
</content>
</entry>
<entry>
<title>tor-hsservice errors: Use Bug for methods that oughtn't to fail</title>
<updated>2023-08-17T12:19:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-17T12:02:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5e047da9cc4017433b7282858a33543587a976ee'/>
<id>urn:sha1:5e047da9cc4017433b7282858a33543587a976ee</id>
<content type='text'>
If the service encouters operational errors, surfacing them here is
not helpful.  So these methods ought to work, if they weren't called
erroneously.
</content>
</entry>
</feed>
