[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-talk] Servers might want to avoid there's a crash bug.

Hi, folks!

There appears to be a crash bug[1] in's IPv6 code that
can get triggered on a server when a client sets the wrong set of IPv6
options.  No cause for major alarm: It doesn't appear to allow remote
code execution or anything -- but it *does* make servers segfault.  So
if you've got a server you don't want crashing, maybe you shouldn't
run on it.

Clients running are likely to be annoyed by the
log-message-spewing bug[2] that Mike's trying to track down.

If you want to track the 0.2.4.x series but you can't bear crashes,
you might want to stay at and wait for or  Or if you're a dauntless soul who wants to try the fix
for the crash issue in [1] to see if it works (or if you're a bug
hipster who wants to experience all the new bugs before anybody else
has even heard of them), just run the master branch from git, version
51c2dd8f8954d5 or later.  Or if you hate unstable branches with a
burning passion, you might want to stick with 0.2.3.x until 0.2.4.x is
farther along on its development cycle.

Sorry for the inconvenience here.  Bugs are always annoying, even when
the release version says "alpha".  I hope everybody has a good new

[1] https://trac.torproject.org/projects/tor/ticket/7814
[2] https://trac.torproject.org/projects/tor/ticket/7799

tor-talk mailing list