Opened 13 years ago

Last modified 7 years ago

#362 closed defect (Won't fix)

Tor crashes after numerous failed name resolutions.

Reported by: Orum Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.1.25
Severity: Keywords:
Cc: Orum Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If a tor exit node is unable to contact a DNS server, after numerous failed name resolution
attempts, tor will crash.

gdb(1) seems to always point to the FreeBSD pthread library when asking "where" post-mortem.
Apologies for not having the exact output, as I have fixed the issue and no longer have the
core (and would like to not break it again).

However, should you be confirming this, the easiest way to replicate this is by setting up a
tor exit node with a relatively unrestricted exit policy (the default should do). Make sure
that tor does *not* query a valid nameserver by modifying your /etc/resolv.conf (easiest way
to do this without breaking DNS on the host machine is to run tor in a chroot(8) or jail(8)
environment) to point to an invalid nameserver. After a few hours (maybe less on high band-
width nodes) tor will crash, dropping it's core.

[Automatically added by flyspray2trac: Operating System: BSD]

Child Tickets

Change History (5)

comment:1 Changed 13 years ago by arma

Was this 0.1.1.25, 0.1.2.3-alpha, or both? They have quite different DNS
systems.

comment:2 Changed 13 years ago by Orum

Sorry, it was in stable, 0.1.1.25.

comment:3 Changed 13 years ago by nickm

This should be irrelevant in the 0.1.2.x series, where we aren't using the platform DNS
any more. If it comes back in the 0.1.2.x series, please let us know. As it is,
I'm going to mark this "won't fix" because the workaround is easy ("fix your DNS.")

comment:4 Changed 13 years ago by nickm

flyspray2trac: bug closed.
see comment

comment:5 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.