10.3.1:
2- Workaround for dropped cell WARNS due to Tor bugs #29699, #29700,
3  #29786, and #29927. These cases are now logged at INFO/NOTICE, with
4  specific Tor bug number for each case. #37
5- Re-apply vanguard config params upon SIGHUP. #40.
6
70.3.0
8-----
9- Apply bandguards limits to non-HS circuits too. #34.
10
110.2.3
12-----
13- Global option to disable circuit killing. #32.
14- Fix config parsing of boolean values. #36.
15- Add tests/default.conf to sdist/pip tarball. #27
16- Do not allow any dropped cells if Tor 0.3.4.10+ is being used. #25 and #3.
17- Retry Tor connection if Tor is missing descriptors at startup. #35.
18- Reorganized README_SECURITY to link to specific mitigation sections for each
19  adversary attack.
20
210.2.2
22-----
23- Fix exception when a connection to a guard is closed with more than one
24  live circuit. #29
25- Catch control+c and exit cleanly. #30.
26- Use Tor's network liveness events to double-check connectivity.
27- Print out relevant versions at startup.
28
290.2.1
30-----
31
32- Read ExcludeNodes from Tor and don't pick layer2 or layer3 guards in this
33  set. #11
34- Add --one_shot_vanguards and --disable_vanguards options (to enable
35  OnionBalance synchronization). #12
36- Don't write to torrc by default. #18
37- Keep attempting to reconnect if the control port dies. #19
38- Support tighter bounds on dropped data to defend against DropMark,
39  and change circ_max_dropped_bytes_percent to circ_max_dropped_cells.
40  However, leave these at NOTICE pending Tor patch #25573. #20.
41- Limit rend requests from relays that are not in our consensus. #22.
42- Added connectivity accounting: WARN if we're disconnected or can't build
43  circuits for more than 'conn_max_disconnected_secs' and
44  'circ_max_disconnected_secs'. Also emit a NOTICE if a connection dies while
45  there are live circuits on it. #23
46- Fix several false positive cases in rendguard. More may remain, so demote
47  logline to NOTICE for now. #24
48- Change rendguard params to lower the false positive rate. If you use a
49  conf file, be sure to update the values there, if specified. #24.
50- Standardize using WARN for messages that we're confident represent
51  serious issues, and use NOTICE for heuristics that may need more tuning.
52
530.1.1
54-----
55
56- Initial release
57