aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Merge commit 'sebastian/quiet'Nick Mathewson2010-01-25
|\
| * Be quieter about failing to decode authority digestsSebastian Hahn2010-01-25
| | | | | | | | | | | | | | This was freaking out some relay operators without good reason, as it is nothing the relay operator can do anything about anyways. Quieting this warning suggested by rieo.
* | Rearrange _thread_test_func to please Coverity ScanNick Mathewson2010-01-25
| | | | | | | | | | | | | | | | I believe that since we were allocating *cp while holding a mutex, coverity deduced that *cp must be protected by that mutex, and later flipped out when we didn't use it that way. If this is so, we can solve our problems by moving the *cp = tor_strdup(buf) part outside of the mutex-protected code.
* | Try to untangle the logic in server_port_flushNick Mathewson2010-01-25
| | | | | | | | | | | | | | | | | | | | | | It's a bit confusing to have a loop where another function, confusingly named "*_free", is responsible for advancing the loop variable (or rather, for altering a structure so that the next time the loop variable's initializer is evaluated it evaluates to something different.) Not only has this confused people: it's also confused coverity scan. Let's fix that.
* | Don't unlock a new log until done logging the tor version.Nick Mathewson2010-01-25
|/ | | | This might please coverity scan.
* Since dump_microdescriptor() can return -1; make its type ssize_tNick Mathewson2010-01-24
|
* Handle errors reported by fwrite() in dump_microdescriptor()Peter Palfrader2010-01-24
| | | | Does not deal with error handling in dump_microdescriptor's callers.
* Merge commit 'origin/maint-0.2.1'Nick Mathewson2010-01-24
|\ | | | | | | | | | | | | Resolved conflicts in: configure.in src/or/Makefile.am src/tools/Makefile.am
| * Add --enable-static-(openssl|libevent) optionsNick Mathewson2010-01-24
| | | | | | | | | | These options only work when using --with-(openssl|libevent)-dir to explicitly pick a libevent or openssl location.
* | Merge remote branch 'origin/maint-0.2.1'Nick Mathewson2010-01-23
|\|
| * Fix two rare leaks spotted by rieo.Nick Mathewson2010-01-23
| |
| * Avoid a possible crash in tls_log_errors.Nick Mathewson2010-01-22
| | | | | | | | | | | | | | | | We were checking for msg==NULL, but not lib or proc. This case can only occur if we have an error whose string we somehow haven't loaded, but it's worth coding defensively here. Spotted by rieo on IRC.
* | Don't use OutboundBindAddress to connect to localhostNick Mathewson2010-01-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The OutboundBindAddress option is useful for making sure that all of your outbond connections use a given interface. But when connecting to 127.0.0.1 (or ::1 even) it's important to actually have the connection come _from_ localhost, since lots of programs running on localhost use the source address to authenticate that the connection is really coming from the same host. Our old code always bound to OutboundBindAddress, whether connecting to localhost or not. This would potentially break DNS servers on localhost, and socks proxies on localhost. This patch changes the behavior so that we only look at OutboundBindAddress when connecting to a non-loopback address.
* | bump to 0.2.2.7-alphaRoger Dingledine2010-01-19
| |
* | 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
| |
* | Merge branch 'maint-0.2.1' into masterRoger Dingledine2010-01-19
|\| | | | | | | | | | | | | | | | | Conflicts: ChangeLog configure.in contrib/tor-mingw.nsi.in src/win32/orconfig.h
| * bump to 0.2.1.22, and give it a changelogRoger Dingledine2010-01-19
| |
| * downgrade a warningRoger Dingledine2010-01-19
| | | | | | | | | | | | | | this case can now legitimately happen, if you have a cached v2 status from moria1, and you run with the new list of dirservers that's missing the old moria1. it's nothing to worry about; the file will die off in a month or two.
| * rotate keys for moria1 and gabelmooRoger Dingledine2010-01-19
| |
| * stop bridge authorities from leaking their bridge listRoger Dingledine2010-01-17
| |
* | Fix build on Solaris by disabling support for DisableAllSwapSebastian Hahn2010-01-19
| | | | | | | | | | Fixes bug 1198. Solaris doesn't have RLIMIT_MEMLOCK for get/setrlimit, so disable support because we don't know if all memory can be locked.
* | Build Bug: -lm should come after passing ../common/libor.a to linkerMichael Witten2010-01-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following commit: commit e56747f9cf29ed788baf8805bfe391925d8a19da Author: Nick Mathewson <nickm@torproject.org> Date: Tue Dec 15 14:32:55 2009 -0500 Refactor a bit so that it is safe to include math.h, and mostly not needed. introduced this line: tor_resolve_LDADD = -lm ../common/libor.a @TOR_LIB_WS32@ which caused the build to fail, because only ../common/libor.a (via the embedded ../common/util.o via ../common/util.c) referenced libm's `lround' and `log' symbols, so that the linker (GNU ld) didn't bother to import those symbols before reading ../common/libor.a, thus leaving those symbols undefined. The solution was to swap the order, producing the line: tor_resolve_LDADD = ../common/libor.a -lm @TOR_LIB_WS32@ Signed-off-by: Michael Witten <mfwitten@gmail.com>
* | Log a notice when we get a new control connectionSebastian Hahn2010-01-18
| |
* | Merge remote branch 'origin/maint-0.2.1'Nick Mathewson2010-01-16
|\| | | | | | | | | | | | | | | Conflicts: ChangeLog configure.in contrib/tor-mingw.nsi.in src/win32/orconfig.h
| * bump to 0.2.1.21 so we can releaseRoger Dingledine2009-12-21
| |
* | whitespace fixesRoger Dingledine2010-01-15
| |
* | fix an impossible-to-actually-trigger overflow in descriptor generationRoger Dingledine2010-01-15
| |
* | resolve path weighting edge case; fixes bug 1203Roger Dingledine2010-01-15
| |
* | trivial cleanupsRoger Dingledine2010-01-15
| |
* | remove redundant validate_addr_policies() checksRoger Dingledine2010-01-15
| |
* | don't warn if stats/bridge-stats is missingRoger Dingledine2010-01-15
| | | | | | | | | | | | | | if we try to read it to publish stats and it's not there, that means there are no stats to publish. reported by swisstorexit.
* | don't list windows capabilities in windows unameRoger Dingledine2010-01-15
| | | | | | | | we never used them, and maybe it's a bad idea to publish them
* | don't div by 0 during path selectionRoger Dingledine2010-01-02
| |
* | when loading bridge stats, mkdir $datadir/stats firstRoger Dingledine2010-01-02
| |
* | add config options to override.Roger Dingledine2009-12-29
| | | | | | | | somebody should add man page entries.
* | add separate per-conn write limitingRoger Dingledine2009-12-29
| |
* | Authorities now support conditional consensusesSebastian Hahn2009-12-25
| | | | | | | | Mark them this way in add_trusted_dir_server
* | Remove some old, commented out codeSebastian Hahn2009-12-25
| |
* | Remove online config descriptions.Sebastian Hahn2009-12-25
| | | | | | | | | | They weren't in sync with reality nor manpage, and only useful to a human who could simply have checked the manpage.
* | Fix a typoSebastian Hahn2009-12-25
| |
* | New consensus params "bwconnrate" and "bwconnburst"Roger Dingledine2009-12-23
| | | | | | | | | | | | | | ...to let us rate-limit client connections as they enter the network. It's controlled in the consensus so we can turn it on and off for experiments. It's starting out off. Based on proposal 163.
* | make the os x tiger compiler shut upRoger Dingledine2009-12-21
| | | | | | | | it's wrong, but that's our problem not its problem
* | a changelog and doc fixes for the strictnodes workRoger Dingledine2009-12-21
| |
* | fix compileRoger Dingledine2009-12-21
| |
* | 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.
generated by cgit v1.2.3 (git 2.45.0) at 2024-11-27 13:45:59 +0000