aboutsummaryrefslogtreecommitdiff
path: root/changes/1863_bwhist
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-01-10 13:06:50 -0500
committerNick Mathewson <nickm@torproject.org>2011-01-10 13:06:50 -0500
commit7e1502c0d1aa0875fba0b26ddcf021bdfa5e11a0 (patch)
tree90495e52ce10a2818207b641e77d35557a904449 /changes/1863_bwhist
parent8dd4ecd14e6e6e886c76c8464595d4f903447c42 (diff)
downloadtor-7e1502c0d1aa0875fba0b26ddcf021bdfa5e11a0.tar.gz
tor-7e1502c0d1aa0875fba0b26ddcf021bdfa5e11a0.zip
Fix bug when parsing bwhist with unexpected Interval
Previously, our state parsing code would fail to parse a bwhist correctly if the Interval was anything other than the default hardcoded 15 minutes. This change makes the parsing less incorrect, though the resulting history array might get strange values in it if the intervals don't match the one we're using. (That is, if stuff was generated in 15 minute intervals, and we read it into an array that expects 30 minute intervals, we're fine, since values can be combined pairwise. But if we generate data at 30 minute intervals and read it into 15 minute intervals, alternating buckets will be empty.) Bugfix on 0.1.1.11-alpha.
Diffstat (limited to 'changes/1863_bwhist')
-rw-r--r--changes/1863_bwhist5
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/1863_bwhist b/changes/1863_bwhist
new file mode 100644
index 0000000000..c1d4d866ce
--- /dev/null
+++ b/changes/1863_bwhist
@@ -0,0 +1,5 @@
+ o Minor bugfixes
+ - Fix a bug in banwidth history state parsing that could have been
+ triggered if a future version of Tor ever changed the timing
+ granularity at which bandwidth history is measured. Bugfix on
+ Tor 0.1.1.11-alpha.