[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r9702: a clearer changelog, and a future todo item (in tor/trunk: . doc)
Date: 2007-03-01 00:04:54 -0500 (Thu, 01 Mar 2007)
New Revision: 9702
a clearer changelog, and a future todo item
--- tor/trunk/ChangeLog 2007-03-01 04:40:43 UTC (rev 9701)
+++ tor/trunk/ChangeLog 2007-03-01 05:04:54 UTC (rev 9702)
@@ -1,4 +1,12 @@
-Changes in version 0.1.2.9-??? - 2007-??-??
+Changes in version 0.1.2.9-rc - 2007-03-??
+ o Major bugfixes (Windows):
+ - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
+ of the usual GCC "%llu". This prevents a bug when saving 64-bit
+ int configuration values: the high-order 32 bits would get
+ truncated. In particular, we were being bitten by the default
+ MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
+ and maybe also bug 397.)
o Minor bugfixes (performance):
- Use OpenSSL's AES implementation on platforms where it's faster.
This could save us as much as 10% CPU usage.
@@ -7,7 +15,7 @@
- Do not rotate onion key immediately after setting it for the first
- o Minor bugfixes (directory servers):
+ o Minor bugfixes (directory authorities):
- Stop calling servers that have been hibernating for a long time
"stable". Also, stop letting hibernating or obsolete servers affect
uptime and bandwidth cutoffs.
@@ -28,11 +36,6 @@
of 2 as indicating that the server is completely bad; it sometimes
means that the server is just bad for the request in question. (may fix
the last of bug 326.)
- - On mingw, use "%I64u" to printf/scanf 64-bit integers, instead of the
- usual GCC "%llu". This prevents a bug when saving 64-bit int
- configuration values on mingw; the high-order 32 bits would get
- truncated. If the value was then reloaded, disaster would
- occur. (Fixes bug 400 and maybe also bug 397.)
- Disable encrypted directory connections when we don't have a server
descriptor for the destination. We'll get this working again in
the 0.2.0 branch.
--- tor/trunk/doc/TODO 2007-03-01 04:40:43 UTC (rev 9701)
+++ tor/trunk/doc/TODO 2007-03-01 05:04:54 UTC (rev 9702)
@@ -412,6 +412,9 @@
+ - when we hit a funny error from a dir request (eg 403 forbidden),
+ but tor is working and happy otherwise, and we haven't seen many
+ such errors recently, then don't warn about it.
- LD_BUG log messages could prepend "Bug: " automatically, so we don't
have to try to remember to.
- More consistent error checking in router_parse_entry_from_string().