Roger Dingledine 5ad126a51b don't cache connect failures from our own circuits ... The connect failure cache had a bad interaction with retrying connections to our guards or bridges when we go offline and then come back online -- while offline we would fail to connect and cache this result, and then when we return we would decline to even attempt to connect, because our failure cache said it wouldn't work. Now only cache connect failures for relays when we connected to them because of somebody else's EXTEND request. Fixes bug 40499; bugfix on 0.3.3.4-alpha.		2021-11-08 05:37:02 -05:00
..
.dummy	Add a .dummy file in the changes directory to stop git from removing it	2015-05-11 11:41:48 -04:00
bug40396	reassess minimum-dir-info when a bridge fails	2021-10-28 20:57:28 -04:00
bug40496	do notice-level log when we resume having enough dir info	2021-10-28 20:57:28 -04:00
bug40497	don't retry entry guards if they're bridges without descriptors	2021-10-28 20:57:28 -04:00
bug40499	don't cache connect failures from our own circuits	2021-11-08 05:37:02 -05:00
ticket26299	changes: Add file for ticket 26299	2021-10-29 09:20:17 -04:00
ticket40494	relay: Don't allow DirPort on non-IPv4	2021-11-03 09:51:46 -04:00
ticket40504	man: Missing OverloadStatistics option in tor.1	2021-11-02 09:51:43 -04:00