| Age | Commit message (Collapse) | Author |
|---|
|
svn:r17893
|
|
service directory authorities.
svn:r17890
|
|
The subversion $Id$ fields made every commit force a rebuild of
whatever file got committed. They were not actually useful for
telling the version of Tor files in the wild.
svn:r17867
|
|
struct for clarity, and change their type to what we actually want to cast them to.
svn:r17784
|
|
documentation: Don't introduce two parameters called n when you're calling an algorithm O(n).
svn:r17783
|
|
svn:r17739
|
|
patch.
svn:r17686
|
|
svn:r17662
|
|
svn:r17018
|
|
svn:r17010
|
|
router stability calculations.
svn:r17003
|
|
svn:r16994
|
|
do not put junk in the dbg-stability.txt file
svn:r16982
|
|
Untested: somebody please run this on an authority and let me know if it is broken.
svn:r16981
|
|
svn:r16967
|
|
svn:r16941
|
|
svn:r14378
|
|
svn:r14377
|
|
Fix all -Wshorten-64-to-32 warnings that appear on my macbook.
svn:r13662
|
|
Recover from bad tracked-since value in mtbf history file. This may finally close bug 537.
svn:r13636
|
|
rather than ints
svn:r13610
|
|
svn:r13586
|
|
would stop building circuits and start refusing connections after
24 hours, since we false believed that Tor was dormant. Reported
by nwf; bugfix on 0.1.2.x.
svn:r13583
|
|
Fix all but 2 DOCDOC items; defer many XXX020s (particularly those where fixing them would fix no bugs at the risk of introducing some bugs).
svn:r13529
|
|
Fix or downgrade a bunch of xxx020 items.
svn:r13527
|
|
Re-tune mempool parametes based on testing on peacetime: use smaller chuncks, free them a little more aggressively, and try very hard to concentrate allocations on fuller chunks. Also, lots of new documentation.
svn:r13484
|
|
svn:r13440
|
|
Add a bunch more code documentation; change the interface of fetch_var_cell_from_buf() so it takes the current link protocol into account and can't get confused by weird command bytes on v1 connections.
svn:r13430
|
|
svn:r13412
|
|
Add more documentation; change the behavior of read_to_buf_tls to be more consistent. Note a longstanding problem with current read/write interfaces.
svn:r13407
|
|
Stamp out a bunch of atoi users; make more tor_parse_long() users check their outputs.
svn:r13395
|
|
Also, dump our bridge router status entries to disk every 30 minutes.
svn:r12871
|
|
Added two XXX020's that we need to think harder about.
svn:r12859
|
|
First wodge of geoip code so bridges can figure out which countries are blocking them.
svn:r12845
|
|
svn:r12786
|
|
svn:r12607
|
|
svn:r12455
|
|
Try to bulletproof the parse logic for router-stability.
svn:r12441
|
|
Mess with the formula for the Guard flag again. Now it requires that you be in the most familiar 7/8 of nodes, and have above median wfu for that 7/8th. See spec for details. Also, log thresholds better.
svn:r12440
|
|
Do not count a server as having any WFU until we have known about it for 18 hours (weighted).
svn:r12261
|
|
Make unverified-consensus get removed when it is accepted or rejected. Make a new get_datadir_fname*() set of functions to eliminate the common code of "get the options, get the datadir, append some stuff".
svn:r12000
|
|
Save weighted-fractional-uptime to disk as well as MTBF. Bump the version on rouer-stability: downgrading to versions earlier than this one will lose your WFU data.
svn:r11835
|
|
Resolve bug 516: Never report our bandwidth-history as over RelayBandwidthRate*NUM_SECS_BW_SUM_INTERVAL.
svn:r11833
|
|
Add a bunch of function documentation; clean up a little code; fix some XXXXs; tag the nonsensical EXTRAINFO_PURPOSE_GENERAL as nonsesnse; note another bit of "do not cache special routers" code to nuke.
svn:r11761
|
|
Track weighted fractional uptime in addition to weighted mtbf: we want to use mtbf for stable, but fractional uptime for guard.
svn:r11456
|
|
0-pad minutes and seconds when displaying weighted mtbf in info logs.
svn:r11324
|
|
Use (and debug) new file-writing functions in order to simplify code that formerly built big strings in RAM.
svn:r11301
|
|
b) raise the max-believable-bandwidth to 10MB/s.
svn:r11258
|
|
Finish implementing and documenting proposal 108: Authorities now use MTBF data to set their stability flags, once they have at least 4 days of data to use.
svn:r11240
|
|
Clean up MTBF storage code. Do not count times that we have been down toward the current run. Handle backward timewarps correctly. Store MTBF data on exit in addition to periodically.
svn:r11225
|
