yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #66276
[Bug 1088611] Re: using random hostnames to detect dns proxies allows for false positives
This bug was fixed in the package cloud-init -
0.7.9-231-g80bf98b9-0ubuntu1
---------------
cloud-init (0.7.9-231-g80bf98b9-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- tests: remove 'yakkety' from releases as it is EOL.
- systemd: make systemd-fsck run after cloud-init.service (LP: #1691489)
- tests: Add initial tests for EC2 and improve a docstring.
- locale: Do not re-run locale-gen if provided locale is system default.
- archlinux: fix set hostname usage of write_file.
[Joshua Powers] (LP: #1705306)
- sysconfig: support subnet type of 'manual'.
- Drop rand_str() usage in DNS redirection detection
[Bob Aman] (LP: #1088611)
-- Scott Moser <smoser@xxxxxxxxxx> Mon, 31 Jul 2017 09:47:34 -0400
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1088611
Title:
using random hostnames to detect dns proxies allows for false
positives
Status in cloud-init:
Fix Committed
Status in cloud-init package in Ubuntu:
Fix Released
Bug description:
The fix that's been applied for bug #974509 checks for the presence of
a redirector by looking of three hostnames, and treating as invalid
any results pointing to a matching address:
- does-not-exist.example.com.
- example.invalid.
- a random, unqualified 32-character alphanumeric hostname.
The last of these carries a small but non-zero risk of colliding with
a real hostname, and there's a small but non-zero risk that this host
points to the same address as something we care about. If possible,
it would be better to not include this random-host lookup in the
algorithm, as somewhere, some day, chances are there will eventually
be a collision, causing an incomprehensible and unreproducible failure
for a user.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1088611/+subscriptions