#31369: HSv3 descriptor support in stem -----------------------------------------+-------------------------------- Reporter: asn | Owner: atagar Type: defect | Status: reopened Priority: Medium | Milestone: Component: Core Tor/Stem | Version: Severity: Normal | Resolution: Keywords: tor-hs onionbalance scaling | Actual Points: Parent ID: #26768 | Points: 9 Reviewer: | Sponsor: Sponsor27-must -----------------------------------------+--------------------------------
Comment (by asn): Hello atagar again, here is another post but this time about '''descriptor encoding'''. I started looking at how to encode an HSv3 descriptor which involves putting valid (and user-defined) values in the right fields plus encrypting and signing the descriptor. It's a pretty big job and I started by doing ed25519 certificate encoding which is certainly needed for this. I had a bit of trouble adapting the certificate.py code to do encoding, since it seems like the `Ed25519CertificateV1` class has been made with parsing in mind, but in this case I will need to provide its raw attributes (keys, etc.) and have it encode them into an actual certificate. How would you do that in terms of changing the class logic? I took a stab at it here: https://github.com/torproject/stem/pull/21 (see last commit). The whole thing works pretty well (see the unittest) but it's very dirty because I made my own class (for encoding) and use the old class for decoding. We need to unify these two classes but I would need your advice as the stem architect here. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31369#comment:12> 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