Feature #7708

Remove resolvconf

Added by intrigeri 2014-07-31 19:59:33 . Updated 2015-07-08 16:32:39 .

Status:
Resolved
Priority:
Low
Assignee:
Category:
Target version:
Tails_2.0
Start date:
2014-07-31
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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.

Subtasks

History

#1 Updated by intrigeri 2014-12-18 12:00:54

  • Priority changed from Normal to Low

Not a blocker, but if not solved in time for Tails/Jessie, then that would become a 2.0 goal.

#2 Updated by intrigeri 2015-07-08 16:28:45

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:7cd74258ccb3d09e0044062237af3762f3880483.

#3 Updated by intrigeri 2015-07-08 16:32:39

  • Subject changed from Consider removing resolvconf to Remove resolvconf
  • Type of work changed from Research to Code