[tor-bugs] #31823 [Core Tor/Stem]: HSv3 descriptor support in stem [encoding]

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Oct 30 22:20:33 UTC 2019


#31823: HSv3 descriptor support in stem [encoding]
-------------------------------------------------+-------------------------
 Reporter:  asn                                  |          Owner:  atagar
     Type:  defect                               |         Status:
                                                 |  needs_review
 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 atagar):

 > I imagine that the feature will be finalized in December

 Are we discussing this branch or something else? I expect to finish this
 branch within a week or so. HSv3 descriptor support will be part of Stem
 1.8.

 > The main reason for me is we won't need to spend time hunting down bugs
 and incompatibilities in Python2.

 Eh. This work is already done and I've dealt with cross version
 compatibility issues for years. Feel free to leave this to me. It's no big
 whoop. :)

 > We will be able to use nice python3 methods like to_bytes(), fromhex()
 and hex().

 We [https://gitweb.torproject.org/stem.git/tree/stem/util/str_tools.py#n89
 already normalize] all throughout our codebase...

 {{{
 % grep -R 'to_bytes\|to_unicode' stem | wc -l
 184
 }}}

 > We might be able to make stronger assumptions on the crypto libraries
 being present.

 Our cryptography requirement is orthogonal to python 2/3 support.
 Regardless of our interpreter we need to perform prereq checks.

 > We won't need to fix the ed25519 python3 code which is hairy crypto
 code.

 Gotcha. If this truly becomes a problem I'll be happy to discuss but for
 the moment at least I don't envision difficulty in making this branch to
 work with all python versions.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31823#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list