Project

General

Profile

Feature #7712

Automatically test hostname leaks

Added by intrigeri almost 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Test suite
Target version:
Start date:
08/01/2014
Due date:
% Done:

100%

QA Check:
Pass
Feature Branch:
test/7712-hostname-leaks
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

It would be good to at least detect hostname leaks caused by the DHCP client, to catch regressions such as #7688 earlier. Presumably, our existing test suite infrastructure that can capture all network traffic and inspect it could be reused here.

(We now have a step to check this as part of our manual test suite, but adding more and more pain there is no real solution.)


Related issues

Related to Tails - Bug #7688: DHCP client leaks hostname "amnesia" Resolved 08/10/2014

Associated revisions

Revision e89319c2 (diff)
Added by Tails developers almost 5 years ago

Automatically test hostname leaks (Closes: #7712).

History

#1 Updated by intrigeri almost 5 years ago

  • Related to Bug #7688: DHCP client leaks hostname "amnesia" added

#2 Updated by intrigeri almost 5 years ago

  • Description updated (diff)

#3 Updated by intrigeri almost 5 years ago

  • Assignee set to intrigeri
  • Target version set to Tails_1.1.1

I'm on it, in the hope it can save me from doing too much manual testing of #7688. We'll see if I manage to get it done soon enough.

#4 Updated by intrigeri almost 5 years ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 50
  • Feature Branch set to test/7712-hostname-leaks

Done, the new "dhcp" feature works fine: fails on 1.1, passes with current experimental (that has bugfix/7688-no-dhcp-send-hostname merged in).

#5 Updated by intrigeri almost 5 years ago

  • Assignee deleted (intrigeri)
  • QA Check set to Ready for QA

#6 Updated by intrigeri almost 5 years ago

  • Assignee set to intrigeri
  • % Done changed from 50 to 30
  • QA Check deleted (Ready for QA)

I'm only testing the default eth0 DCHP connection, but other kinds of connections could possibly behave differently. I'll try to test those too.

#7 Updated by intrigeri almost 5 years ago

  • Assignee deleted (intrigeri)
  • % Done changed from 30 to 50
  • QA Check set to Ready for QA

#8 Updated by intrigeri almost 5 years ago

  • Assignee set to anonym

I don't see who else that anonym can review this.

#9 Updated by anonym over 4 years ago

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#10 Updated by anonym over 4 years ago

  • Status changed from Fix committed to Resolved

Also available in: Atom PDF