tor - Transit encryption and privacy out of the box

Age	Commit message (Collapse)	Author
2018-07-05	Move literally everything out of src/or	Nick Mathewson
	This commit won't build yet -- it just puts everything in a slightly more logical place. The reasoning here is that "src/core" will hold the stuff that every (or nearly every) tor instance will need in order to do onion routing. Other features (including some necessary ones) will live in "src/feature". The "src/app" directory will hold the stuff needed to have Tor be an application you can actually run. This commit DOES NOT refactor the former contents of src/or into a logical set of acyclic libraries, or change any code at all. That will have to come in the future. We will continue to move things around and split them in the future, but I hope this lays a reasonable groundwork for doing so.
2018-06-21	Rectify include paths (automated).	Nick Mathewson
	You have no idea how glad I am that this is automated.
2018-06-20	Run rectify_include_paths.py	Nick Mathewson

2018-06-20	Update copyrights to 2018.	Nick Mathewson

2017-09-15	Run our #else/#endif annotator on our source code.	Nick Mathewson

2017-03-15	Run the copyright update script.	Nick Mathewson

2016-02-27	Update the copyright year.	Nick Mathewson

2015-09-23	New AuthDirPinKeys option to enable/disable keypinning enforcement	Nick Mathewson
	Implements ticket #17135. We're going to need this one to avoid chaos as everybody figures out how ed25519 keys work.
2015-05-28	Tie key-pinning logic into directory authority operation	Nick Mathewson
	With this patch: * Authorities load the key-pinning log at startup. * Authorities open a key-pinning log for writing at startup. * Authorities reject any router with an ed25519 key where they have previously seen that ed25519 key with a different RSA key, or vice versa. * Authorities warn about, but do not reject, RSA-only descriptors when the RSA key has previously gone along with an Ed25519 key. (We should make this a 'reject' too, but we can't do that until we're sure there's no legit reason to downgrade to 0.2.5.)
2015-05-28	Key-pinning back-end for directory authorities.	Nick Mathewson
	This module implements a key-pinning mechanism to ensure that it's safe to use RSA keys as identitifers even as we migrate to Ed25519 keys. It remembers, for every Ed25519 key we've seen, what the associated Ed25519 key is. This way, if we see a different Ed25519 key with that RSA key, we'll know that there's a mismatch. We persist these entries to disk using a simple format, where each line has a base64-encoded RSA SHA1 hash, then a base64-endoded Ed25519 key. Empty lines, misformed lines, and lines beginning with a # are ignored. Lines beginning with @ are reserved for future extensions.