Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file - Debian

This is a discussion on Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file - Debian ; Package: general Severity: normal The impact of a misconfigured /etc/hosts file can be quite grave. Prime example: If the hostname is not in /etc/hosts, sudo does not run which means that the problem can not be resolved without direct root ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file

  1. Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file

    Package: general
    Severity: normal

    The impact of a misconfigured /etc/hosts file can be quite grave.

    Prime example: If the hostname is not in /etc/hosts, sudo does not run
    which means that the problem can not be resolved without direct root
    login or single user mode. See also bug #473827

    Also, misconfiguration can lead to that the local hostname is resolved
    on the network, causing latency whenever it is requested, such as when
    launching applications, sudo, etc etc. This effect should be minimized.


    -- System Information:
    Debian Release: lenny/sid
    APT prefers testing
    APT policy: (500, 'testing')
    Architecture: powerpc (ppc)

    Kernel: Linux 2.6.22-3-powerpc
    Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
    Shell: /bin/sh linked to /bin/bash



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file

    On 01-Apr-08, 16:13 (CDT), Ulrik Sverdrup wrote:
    > Package: general
    > Severity: normal
    >
    > The impact of a misconfigured /etc/hosts file can be quite grave.
    >
    > Prime example: If the hostname is not in /etc/hosts, sudo does not run
    > which means that the problem can not be resolved without direct root
    > login or single user mode. See also bug #473827


    I can't duplicate this, on a up to date lenny system. Even
    commenting-out all the IP4 addresses didn't cause a problem.

    Removing /etc/hostname *and* /etc/resolv.conf causes:

    $ sudo -s
    sudo: unable to resolve host orca
    root@orca:~#

    But it still works.

    Steve
    --
    Steve Greenland
    The irony is that Bill Gates claims to be making a stable operating
    system and Linus Torvalds claims to be trying to take over the
    world. -- seen on the net



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file

    2008/4/2, Steve Greenland :
    > On 01-Apr-08, 16:13 (CDT), Ulrik Sverdrup wrote:
    > > Package: general
    > > Severity: normal
    > >
    > > The impact of a misconfigured /etc/hosts file can be quite grave.
    > >
    > > Prime example: If the hostname is not in /etc/hosts, sudo does not run
    > > which means that the problem can not be resolved without direct root
    > > login or single user mode. See also bug #473827

    >
    >
    > I can't duplicate this, on a up to date lenny system. Even
    > commenting-out all the IP4 addresses didn't cause a problem.
    >
    > Removing /etc/hostname *and* /etc/resolv.conf causes:
    >
    > $ sudo -s
    > sudo: unable to resolve host orca
    > root@orca:~#
    >
    > But it still works.
    >
    > Steve


    When I encountered this, described briefly but a bit more in #473827,
    I didn't see anything as long as I had network/internet access.
    However, when totally offline, the bug triggered. Thus you could try
    to pull out the network cable and try again. I'll have to come up with
    a practical restore method before trying to reproduce it myself
    though.

    Ulrik



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file

    On 01-Apr-08, 17:22 (CDT), Ulrik Sverdrup wrote:
    >
    > When I encountered this, described briefly but a bit more in #473827,
    > I didn't see anything as long as I had network/internet access.
    > However, when totally offline, the bug triggered. Thus you could try
    > to pull out the network cable and try again. I'll have to come up with
    > a practical restore method before trying to reproduce it myself
    > though.


    Pulling the cable on eth0: no change - error message, but sudo works

    Trying 'ifdown lo': now sudo has wait for a timeout of some sort, but
    eventually it still printed error, and worked.

    (All still with no resolv.conf or hostname file, and hosts with no IPv4
    info.)

    Steve
    --
    Steve Greenland
    The irony is that Bill Gates claims to be making a stable operating
    system and Linus Torvalds claims to be trying to take over the
    world. -- seen on the net



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  5. Bug#473828: marked as done (hosts: Unreasonable impact of misconfigured /etc/hosts file)


    Your message dated Wed, 2 Apr 2008 00:11:59 +0100
    with message-id <200804020112.00344.holger@layer-acht.org>
    and subject line Re: Bug#473828: hosts: Unreasonable impact of misconfigured /etc/hosts file
    has caused the Debian Bug report #473828,
    regarding hosts: Unreasonable impact of misconfigured /etc/hosts file
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system
    misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    473828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473828
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


+ Reply to Thread