| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Basically, all this means is downgrading our warning messages to debug
messages, since the bug workaround code here is adequate to stop the
bug.
|
|
|
|
If we ever add an event, then set it, then add it again, there will be
now two pointers to the event in the event base. If we delete one and
free it, the first pointer will still be there, and possibly cause a
crash later.
This patch adds detection for this case to the code paths in
eventdns.c, and works around it. If the warning message ever
displays, then a cleverer fix is in order.
{I am not too confident that this *is* the fix, since bug 957 is very
tricky. If it is, it is a bugfix on 0.2.0.}
|
|
and cert from disk. Bugfix on 0.2.0.1-alpha.
|
|
When we got a descriptor that we (as an authority) rejected as totally
bad, we were freeing it, then using the digest in its RAM to look up its
download status. Caught by arma with valgrind. Bugfix on 0.2.1.9-alpha.
|
|
|
|
|
|
The trick is that we should assert that our next_mem pointer has not
run off the end of the array _before_ we realign the pointer, since
doing that could take us over the end... but only if we're on a system
where malloc() gives us ram in increments smaller than sizeof(void*).
|
|
|
|
|
|
|
|
Bridges are not supposed to publish router descriptors to the directory
authorities. It defeats the point of bridges when they are included in the
public relay directory.
This patch puts out a warning and exits when the node is configured as
a bridge and to publish v1, v2, or v3 descriptors at the same time.
Also fixes part of bug 932.
|
|
This fixes bug 932, where all of our usage totals for users when we
were a regular server would get included in the extrainfo document.
|
|
This matters because a cpuworker can close its socket when it
finishes. Cpuworker typically runs in another thread, so without a
lock here, we can have a race condition and get confused about how
many sockets are open. Possible fix for bug 939.
|
|
This addresses the first part of bug 918. Users are now warned when
they try to use hibernation in combination with a port below 1024
when they're not on Windows. We don't want to die here, because
people might run Tor as root, use a capabilities system or some
other platform that will allow them to re-attach low ports.
Wording suggested by Marian
|
|
(Don't crash immediately if we have leftover chunks to free after
freeing chunks in a buffer freelist; instead log a debugging message
that might help.)
|
|
|
|
|
|
|
|
|
|
svn:r19377
|
|
svn:r19369
|
|
svn:r19367
|
|
packet filter.
svn:r19356
|
|
bridge detection.
svn:r19355
|
|
svn:r19340
|
|
svn:r19337
|
|
svn:r19307
|
|
svn:r19306
|
|
bytes (aka 20KB/s), to match our documentation. Also update
directory authorities so they always assign the Fast flag to relays
with 20KB/s of capacity. Now people running relays won't suddenly
find themselves not seeing any use, if the network gets faster
on average.
svn:r19305
|
|
torrc.sample.in, so unix people don't shoot themselves in the foot.
svn:r19304
|
|
now avoid using begin_dir for all direct connections.
svn:r19296
|
|
svn:r19295
|
|
svn:r19293
|
|
me further)
svn:r19292
|
|
IP address changes: directory mirrors were mistakenly telling them
their old address if they asked via begin_dir, so they never got
an accurate answer about their new address, so they just vanished
after a day. Should fix bugs 827, 883, and 900 -- but alas, only
after every directory mirror has upgraded.
svn:r19291
|
|
version. otherwise there's no reason to tell the user we're
doing behind-the-scenes cleaning.
svn:r19288
|
|
ago. This change should significantly improve client performance,
especially once more people upgrade, since relays that have been
a guard for a long time are currently overloaded.
svn:r19287
|
|
svn:r19273
|
|
svn:r19262
|
|
svn:r19261
|
|
This makes bridge lines a bit smaller and easier for users to
understand.
Also, remove a duplicate changelog entry from the past.
svn:r19260
|
|
operator changed the bandwithrate or bandwithburst settings.
svn:r19259
|
|
is set
svn:r19257
|
|
fuzzing found the rest.
svn:r19250
|
|
svn:r19248
|
|
to help track whether we received them when a relay operator claims
they got sent.
svn:r19213
|
