#21900: evdns fails when resolv.conf is missing, but succeeds when resolv.conf is empty -------------------------------------------------+------------------------- Reporter: teor | Owner: Type: defect | Status: new Priority: Medium | Milestone: Tor: | 0.3.2.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: technical-debt, dns, crash, tor- | Actual Points: relay, macos | Parent ID: | Points: 2 Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by teor): Replying to [comment:1 teor]: > Also, if you issue a SETCONF to tor while it's in this state, it will abort with: > > [err] set_options: Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.2.9.9 008f2846b9b53d52) > > This is not such an important crash, because it only happens on platforms which remove resolv.conf (which as far as I know, is only macOS when the network is down). And I think it only happens on relays, not clients. But it would still be nice to fix it. Tor Browser could trigger this crash by issuing a SETCONF when the network is down, but it doesn't use local DNS in the default config, so I think that's ok. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21900#comment:3> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs