public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "berend.de.schouwer at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/13935] getaddrinfo NXDOMAIN hijack exploit for hosts with two-component hostnames
Date: Thu, 12 Sep 2013 08:35:00 -0000	[thread overview]
Message-ID: <bug-13935-131-68LGDJ43XI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13935-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=13935

Berend <berend.de.schouwer at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |berend.de.schouwer at gmail dot co
                   |                            |m

--- Comment #6 from Berend <berend.de.schouwer at gmail dot com> ---
As a workaround you can try 'domain .'  WorksForMe(tm); but the file does get
overwritten by NetworkManager.

getdomainname(2) still returns the actual domainname, in my simplistic tests.

I stumbled across this from a slightly different angle:
- the corporate network sets the hostname.
- connecting over a non-corporate network then keeps the machine hostname, but
'search ...' is blank.
- externally the corporate network then ends up giving wildcards when there's a
failed lookup.

The end result is the same: typos result in answers rather than NXDOMAIN.

I'm for disabling implicit search lists if 'search ...' is blank.  I'll add
network-specific search lists as I connect.

(I also want the corporate DNS to not do this -- and have queried that
internally, but DNS lookups end me on sedoparking eventually)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-09-12  8:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01 20:16 [Bug network/13935] New: " nagle at sitetruth dot com
2012-04-01 21:06 ` [Bug network/13935] " nagle at sitetruth dot com
2012-04-01 22:20 ` nagle at sitetruth dot com
2012-04-02 17:35 ` ppluzhnikov at google dot com
2012-04-04  2:51 ` nagle at sitetruth dot com
2012-08-24 10:48 ` scorneli at redhat dot com
2012-08-24 16:46 ` nagle at sitetruth dot com
2012-08-24 17:31 ` law at redhat dot com
2012-11-03 17:01 ` karme at karme dot de
2013-09-12  8:35 ` berend.de.schouwer at gmail dot com [this message]
2014-02-16 19:42 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2014-06-25 11:24 ` fweimer at redhat dot com
2020-06-22 13:40 ` fweimer at redhat dot com
2020-06-22 13:43 ` carlos at redhat dot com
2020-06-22 13:44 ` fweimer at redhat dot com
2020-06-22 13:58 ` schwab@linux-m68k.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13935-131-68LGDJ43XI@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).