Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #363
Closed (moved) (moved)
Open
Issue created Nov 26, 2006 by Trac@tracbot

Refuse to start if /etc/resolv.conf cannot be read/parsed

Tor exit nodes currently assume a local nameserver listening on 127.0.0.1 if /etc/resolv.conf cannot be found (or parsed, I would assume). However, in order to mitigate DNS issues with exit nodes (i.e. those described in task #362 (moved)), I think tor should refuse to start (or at least log a warning/error to stderr) if this is the case. Of course, this does not solve all DNS issues, as invalid DNS servers could still easily exist in /etc/resolv.conf, but it will at least act as a basic "dummy proofing" for those chrooting/jailing their tor exit nodes.

[Automatically added by flyspray2trac: Operating System: All]

Trac:
Username: Orum

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking