aboutsummaryrefslogtreecommitdiff
path: root/src/or/circuitbuild.c
Commit message (Collapse)AuthorAge
...
| * | Update Tor Project copyright yearsNick Mathewson2010-02-27
| | |
* | | Merge remote branch 'origin/maint-0.2.1'Nick Mathewson2010-02-27
|\| | | | | | | | | | | | | | | | | Conflicts: ChangeLog src/or/routerparse.c
| * | Proper NULL checking in circuit_list_path_impl()Sebastian Hahn2010-02-26
| | | | | | | | | | | | | | | | | | | | | Another dereference-then-NULL-check sequence. No reports of this bug triggered in the wild. Fixes bugreport 1256. Thanks to ekir for discovering and reporting this bug.
* | | Remove misc unnecessary newlines found by new check.Mike Perry2010-02-22
| | |
* | | Always weight routers by bandwidth.Mike Perry2010-02-22
| |/ |/| | | | | | | Also always predict that we need a high capacity circuit or internal circuit.
* | Describe the recent timeouts reallocation behavior.Mike Perry2010-02-18
| |
* | Move CBT params into consensus.Mike Perry2010-02-18
| |
* | Add an event for a case where we drop guards.Mike Perry2010-02-18
| | | | | | | | Also add a comment about an odd CBT timeout edgecase.
* | Add BUILDTIMEOUT_SET event for CBT stress testing.Mike Perry2010-02-18
| |
* | Merge branch 'maint-0.2.1'Roger Dingledine2010-01-19
|\| | | | | | | | | | | Conflicts: ChangeLog
| * spread guard rotation out throughout the monthRoger Dingledine2010-01-19
| |
| * weight guard choice by bandwidth; discard old guardsRoger Dingledine2010-01-19
| |
| * read the "circwindow" parameter from the consensusRoger Dingledine2009-10-14
| | | | | | | | | | backport of c43859c5c12361fad505 backport of 0d13e0ed145f4c1b5bd1
* | make the os x tiger compiler shut upRoger Dingledine2009-12-21
| | | | | | | | it's wrong, but that's our problem not its problem
* | Use nodes in ExitNodes even if they're not fast/stableRoger Dingledine2009-12-21
| |
* | Use nodes in EntryNodes even if they're not fast/stableRoger Dingledine2009-12-21
| |
* | instrument entry_is_live to tell why our guard isn't liveRoger Dingledine2009-12-21
| |
* | Be more willing to use an unsuitable circuit for exit.Roger Dingledine2009-12-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifically, there are two cases: a) are we willing to start a new circuit at a node not in your ExitNodes config option, and b) are we willing to make use of a circuit that's already established but has an unsuitable exit. Now we discard all your circuits when you set ExitNodes, so the only way you could end up with an exit circuit that ends at an unsuitable place is if we explicitly ran out of exit nodes, StrictNodes was 0, and we built this circuit to solve a stream that needs solving. Fixes bug in dc322931, which would ignore the just-built circuit because it has an unsuitable exit.
* | Make EntryNodes config option much more aggressive.Roger Dingledine2009-12-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Before it would prepend your requested entrynodes to your list of guard nodes, but feel free to use others after that. Now it chooses only from your EntryNodes if any of those are available, and only falls back to others if a) they're all down and b) StrictNodes is not set. Also, now we refresh your entry guards from EntryNode at each consensus fetch (rather than just at startup and then they slowly rot as the network changes). The goal here is to make users less likely to set StrictNodes, since it's doing closer to what they expect it should be doing.
* | Switch to a StrictNodes config option.Roger Dingledine2009-12-21
| | | | | | | | | | | | This is step one of handling ExcludedNodes better. This first step is just to make EntryNodes and ExitNodes do what they did before.
* | Merge branch 'safelogging2'Nick Mathewson2009-12-15
|\ \ | | | | | | | | | | | | Conflicts: ChangeLog
| * | Refactor the safe_str_*() API to make more sense.Nick Mathewson2009-12-15
| | | | | | | | | | | | | | | | | | The new rule is: safe_str_X() means "this string is a piece of X information; make it safe to log." safe_str() on its own means "this string is a piece of who-knows-what; make it safe to log".
| * | Allow SafeLogging to exclude client related informationSebastian Hahn2009-12-12
| | |
* | | Refactor a bit so that it is safe to include math.h, and mostly not needed.Nick Mathewson2009-12-15
| | |
* | | Now that FOO_free(NULL) always works, remove checks before calling it.Nick Mathewson2009-12-12
| | |
* | | *_free functions now accept NULLSebastian Hahn2009-12-12
|/ / | | | | | | | | | | | | | | Some *_free functions threw asserts when passed NULL. Now all of them accept NULL as input and perform no action when called that way. This gains us consistence for our free functions, and allows some code simplifications where an explicit null check is no longer necessary.
* | Remove checks for array existence. (CID 410..415)Nick Mathewson2009-10-26
| | | | | | | | | | | | | | | | | | | | | | | | In C, the code "char x[10]; if (x) {...}" always takes the true branch of the if statement. Coverity notices this now. In some cases, we were testing arrays to make sure that an operation we wanted to do would suceed. Those cases are now always-true. In some cases, we were testing arrays to see if something was _set_. Those caes are now tests for strlen(s), or tests for !tor_mem_is_zero(d,len).
* | fix compile on windowsRoger Dingledine2009-10-11
| |
* | Fix a memleak when throwing away some build timesSebastian Hahn2009-10-10
| | | | | | | | | | This was introduced in f7e6e852e80c22b40a8f09bc1c85074726d7078e. Found by Coverity
* | Tweak an assert that shouldn't fire either way.Mike Perry2009-10-07
| | | | | | | | | | | | There were however other places where we used to call this function that might have caused this to fire. Better safe than sorry now.
* | Tweak values for when to discard all of our history.Mike Perry2009-10-07
| | | | | | | | | | | | This seems to be happening to me a lot on a garbage DSL line. We may need to come up with 2 threshholds: a high short onehop count and a lower longer count.
* | Remove another overzealous assert.Mike Perry2009-10-07
| | | | | | | | Pretimeouts may have build time data, just no timeout data.
* | try to stem the 'sea of fail'Roger Dingledine2009-10-01
| |
* | Ignore one-hop circuits for circuit timeout calcRoger Dingledine2009-10-01
| | | | | | | | | | | | Don't count one-hop circuits when we're estimating how long it takes circuits to build on average. Otherwise we'll set our circuit build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
* | Fix 1108: Handle corrupt or large build times state.Mike Perry2009-09-29
| | | | | | | | | | | | 1108 was actually just a fencepost error in an assert, but making the state file handling code resilient is a good idea.
* | Fix memory leakSebastian Hahn2009-09-27
| | | | | | | | | | | | | | Some memory could be lost in the error case of circuit_build_times_parse_state. Found by Coverity
* | Fix Bug 1103.Mike Perry2009-09-21
| | | | | | | | | | Don't pass in a quantile that is too high during pretimeout calcualtion.
* | Change the condition on the nonlive timeout counting.Mike Perry2009-09-20
| | | | | | | | Try to clarify things in the comment too.
* | Fix typos and comments, plus two bugsRoger Dingledine2009-09-20
| | | | | | | | | | | | | | | | A) We were considering a circuit had timed out in the special cases where we close rendezvous circuits because the final rendezvous circuit couldn't be built in time. B) We were looking at the wrong timestamp_created when considering a timeout.
* | Implement and document new network liveness algorithm.Mike Perry2009-09-20
| | | | | | | | Based on irc discussion with arma.
* | Fix some precision-related asserts in unit tests.Mike Perry2009-09-20
| | | | | | | | | | Mostly by storing the timeout as milliseconds and not seconds internally.
* | Fix compile on freebsdSebastian Hahn2009-09-18
| |
* | give proposal 151 a changelog and other touchupsRoger Dingledine2009-09-17
| |
* | Clarify use of magic number 0.98 with #define.Mike Perry2009-09-16
| |
* | Fix unit tests and compile issues on Snow LeopardSebastian Hahn2009-09-16
| |
* | Change liveness value to be a function of the timeout.Mike Perry2009-09-16
| | | | | | | | | | And also the number of recent circuits used to decide when the network changes.
* | Add log message so we have accurate build time values.Mike Perry2009-09-16
| |
* | Address nickm's issues from his review #1.Mike Perry2009-09-16
| |
* | Move circuitbuildtimeout config check.Mike Perry2009-09-16
| | | | | | | | | | | | | | We want it to be under our control so it doesn't mess up initialization. This is likely the cause for the bug the previous assert-adding commit (09a75ad) was trying to address.
* | Time for some debugging by asserts.Mike Perry2009-09-16
| | | | | | | | Got a negative timeout value on startup. Need to narrow it down.
generated by cgit v1.2.3 (git 2.49.0) at 2025-04-17 19:42:36 +0000