Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 960
    • Issues 960
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #7708

Closed
Open
Created Jul 31, 2014 by intrigeri@intrigeriMaintainer

Remove resolvconf

Originally created by @intrigeri on #7708 (Redmine)

Removing resolvconf would make our configuration tree, build system and runtime configuration a bit simpler, less kludgy, easier to hack and to audit.

We use resolvconf to ensure the nameserver in /etc/resolv.conf is always pointing to 127.0.0.1. Our Tor_enforcement/DNS design doc says it’s here so that NetworkManager and dhclient don’t modify resolv.conf.

  • On Jessie, according to NetworkManager.conf(5), one can use “dns=none”, so that NM never modifies resolv.conf.
  • For dhclient, we can redefine the make_resolv_conf function to be a no-op, via a /etc/dhcp/dhclient-enter-hooks.d/ hook, just like resolvconf does.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tails_2.0
Milestone
Tails_2.0 (Past due)
Assign milestone
Time tracking
None
Due date
None