Project

General

Profile

Bug #11720

DHCP requests leak hostname on Stretch

Added by intrigeri about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
08/25/2016
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:


Related issues

Related to Tails - Bug #11630: Check what to do wrt. NetworkManager's internal DHCP client vs. isc-dhcp-client Resolved 08/11/2016
Related to Tails - Bug #16365: Rebase our custom NetworkManager package on top of 1.6.2-3+deb9u2 Resolved 01/16/2019

Associated revisions

Revision a0158d97 (diff)
Added by intrigeri about 3 years ago

Drop obsolete NM configuration wrt. sending hostname in DHCP requests, and update design doc to reflect what is really happening in Tails 3.x.

Closes: #11720

History

#1 Updated by intrigeri about 3 years ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

I have a fix that seems to work locally, but we need a new automated test: adding new connection without providing the complete config file, e.g. using the GUI or nmcli. Rationale: by providing a complete config file, that says dhcp-send-hostname=false, we are not testing what would happen with a connection added like users do.

#2 Updated by intrigeri about 3 years ago

My fix does not work for newly added connections. Next things to try:

  • drop customization of the list of plugins
  • set dhcp-send-hostname=false directly in NetworkManager.conf
  • set dhcp-send-hostname=false in a [ip] block
  • set dhcp-send-hostname=false in a [ip4] block

#3 Updated by intrigeri about 3 years ago

  • Related to Bug #11630: Check what to do wrt. NetworkManager's internal DHCP client vs. isc-dhcp-client added

#4 Updated by intrigeri about 3 years ago

  • Description updated (diff)

#5 Updated by intrigeri about 3 years ago

  • % Done changed from 10 to 20

So, what we need is apparently not supported in NM (and it might have been pure luck that it worked as we wanted in the past). I've commented on the upstream bug (see description). Until this is fixed on their side, our best option is probably to patch NetworkManager so that it never adds the config line about sending hostname in the dhclient configuration it generates.

#6 Updated by intrigeri about 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100

#7 Updated by intrigeri 10 months ago

  • Related to Bug #16365: Rebase our custom NetworkManager package on top of 1.6.2-3+deb9u2 added

Also available in: Atom PDF