| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| | |
Conflicts:
src/common/util.c
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This is needed for IOCP, since telling the IOCP backend about all
your CPUs is a good idea. It'll also come in handy with asn's
multithreaded crypto stuff, and for people who run servers without
reading the manual.
|
| | |
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Thanks to Sebastian for his code-review of the bufferevents patch series.x
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This requires the latest Git version of Libevent as of 24 March 2010.
In the future, we'll just say it requires Libevent 2.0.5-alpha or
later.
Since Libevent doesn't yet support hierarchical rate limit groups,
there isn't yet support for tracking relayed-bytes separately when
using the bufferevent system. If a future version does add support
for hierarchical buckets, we can add that back in.
|
| | |
|
| |
| |
| |
| |
| | |
Clients are now verified to work and build circuits correctly. There
are still a few warnings given here and there that I need to look into.
|
| |
| |
| |
| | |
Add an --enable-bufferevents config switch.
|
|\ \
| |/
|/| |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This function uses GetSystemDirectory() to make sure we load the version
of the library from c:\windows\system32 (or local equivalent) rather than
whatever version lives in the cwd.
|
|\ \
| |/
|/| |
|
| | |
|
| |
| |
| |
| |
| | |
I think there was a read-off-the-end-of-the-buffer bug that I fixed.
At least I added some good comments, I hope.
|
| | |
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This should keep WinCE working (unicode always-on) and get Win98
working again (unicode never-on).
There are two places where we explicitly use ASCII-only APIs, still:
in ntmain.c and in the unit tests.
This patch also fixes a bug in windoes tor_listdir that would cause
the first file to be listed an arbitrary number of times that was
also introduced with WinCE support.
Should fix bug 1797.
|
| | |
|
|/
|
|
| |
Incidentally fixes bug 1042.
|
|\ |
|
| |
| |
| |
| |
| | |
The getrlimit call didn't have any effect. Also make some logging
less verbose on default log level, and refactor a bit.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This should make us conflict less with system files named "log.h".
Yes, we shouldn't have been conflicting with those anyway, but some
people's compilers act very oddly.
The actual change was done with one "git mv", by editing
Makefile.am, and running
find . -name '*.[ch]' | xargs perl -i -pe 'if (/^#include.*\Wlog.h/) {s/log.h/torlog.h/; }'
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Possible workaround for bug 1139, if anybody cares.
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
From the code:
zlib 1.2.4 and 1.2.5 do some "clever" things with macros. Instead of
saying "(defined(FOO) ? FOO : 0)" they like to say "FOO-0", on the theory
that nobody will care if the compile outputs a no-such-identifier warning.
Sorry, but we like -Werror over here, so I guess we need to define these.
I hope that zlib 1.2.6 doesn't break these too.
Possible fix for bug 1526.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Older versions of Libevent forgot to declare enough function arguments
constant.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These timers behave better with non-monotonic clocks than our old
ones, and also try harder to make once-per-second events get called
one second apart, rather than one-plus-epsilon seconds apart.
This fixes bug 943 for everybody using Libevent 2.0 or later.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
This should never happen unless openssl is buggy or some of our
assumptions are deeply wrong, but one of those might have been the
cause of the not-yet-reproducible bug 1209. If it ever happens again,
let's get some info we can use.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Having ~/.tor expand into /.tor is, after all, almost certainly not
what the user wanted, and it deserves a warning message.
Also, convert a guess-and-malloc-and-sprintf triple into an asprintf.
|
| | |
| | |
| | |
| | | |
This means Tor no longer dies when it doesn't have a $HOME.
|
| | | |
|