#31823: HSv3 descriptor support in stem [encoding]
-------------------------------------------------+-------------------------
Reporter: asn | Owner: atagar
Type: defect | Status:
| needs_revision
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Stem | Version:
Severity: Normal | Resolution:
Keywords: tor-hs scaling onionbalance | Actual Points: 2
network-team-roadmap-september tor-spec |
Parent ID: #26768 | Points: 5
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by asn):
Replying to [comment:14 atagar]:
>
> Is that what you would like? The base64 encoding of a random key? If so
that's a very simple tweak to make. Or are you requesting something else?
Yep, that's good for the `desc-auth-ephemeral-key` part!
Yep, my wrong for not documenting why client auth values were fabricated
like that. The reason is that's actually also what little-t-tor does, so
ideally we would blend in as well. Here is how tor.git makes fake auth-
client entries
(https://github.com/torproject/tor/blob/master/src/feature/hs/hs_descriptor.c#L2852)
and here how it calculates the number of fakes to add
(https://github.com/torproject/tor/blob/master/src/feature/hs/hs_service.c#L1794).
For stem we can just always add 16 fake auth client lines and that's good
enough for now (since stem does not have support for actual client
authorization yet).
----
Other than that, key blinding works just fine now over here! I also
replide on the other PR comments!
I will keep on testing and reviewing in the meanwhile while I develop
onionbalance. Thanks for the help!
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31823#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
