[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9380 [BridgeDB]: Increase strictness of descriptor parsers according to spec
#9380: Increase strictness of descriptor parsers according to spec
-----------------------------+-----------------
Reporter: sysrqb | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: BridgeDB | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-----------------------------+-----------------
Comment (by atagar):
> atagar, thoughts? Basically, we need to parse bridge descriptors, extra-
info descriptors, and networkstatuses and retrieve ~10% of the information
they contain.
Hi sysrqb. Yup, this would be a perfect use case for stem. I assume by
'bridge descriptors' you mean 'bridge variant of server descriptors' in
which case yup, we have support for all of those...
*
[https://stem.torproject.org/api/descriptor/server_descriptor.html#stem.descriptor.server_descriptor.BridgeDescriptor
Bridge Server Descriptor]
*
[https://stem.torproject.org/api/descriptor/extrainfo_descriptor.html#stem.descriptor.extrainfo_descriptor.BridgeExtraInfoDescriptor
Bridge Extrainfo Descriptor]
* [https://stem.torproject.org/api/descriptor/networkstatus.html Network
Status Documents] (though these, of course, don't contain bridges)
If you have need of a descriptor parser then I definitely think it would
be worth snagging stem. Stem does rather strict validation of the content
(which you're looking for) and has quite a bit of tests around these
modules. Also, I keep it up to date with the specs.
Cheers! -Damian
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9380#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs