History

Nick Mathewson 4893e9a15f Migrate tor-netdoc from chrono to time 0.3 (This appears to be the emerging consensus of how to handle RUSTSEC-2020-0159.)		2021-10-24 10:50:21 -04:00
..
fuzz	Update corpus and links.	2021-09-07 12:32:50 -04:00
src	Migrate tor-netdoc from chrono to time 0.3	2021-10-24 10:50:21 -04:00
testdata	Move all crates into a `crates` subdirectory.	2021-08-27 09:53:09 -04:00
Cargo.toml	Migrate tor-netdoc from chrono to time 0.3	2021-10-24 10:50:21 -04:00
README.md	Move all crates into a `crates` subdirectory.	2021-08-27 09:53:09 -04:00

README.md

tor-netdoc

Parse and represent directory objects used in Tor.

Overview

Tor has several "directory objects" that it uses to convey information about relays on the network. They are documented in dir-spec.txt.

This crate has common code to parse and validate these documents. Currently, it can handle the metaformat, along with certain parts of the router descriptor type. We will eventually need to handle more types.

This crate is part of Arti, a project to implement Tor in Rust.

Design notes

The crate is derived into three main parts. In the (private) parse module, we have the generic code that we use to parse different kinds of network documents. In the [types] module we have implementations for parsing specific data structures that are used inside directory documents. Finally, the [doc] module defines the parsers for the documents themselves.

Caveat haxxor: limitations and infelicities

TODO: This crate requires that all of its inputs be valid UTF-8: This is fine only if we assume that proposal 285 is implemented in mainline Tor.

TODO: This crate has several pieces that could probably be split out into other smaller cases, including handling for version numbers and exit policies.

TODO: Many parts of this crate that should eventually be public aren't.

TODO: this crate needs far more tests!

License: MIT OR Apache-2.0