[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#789475: marked as done (udhcpc: valid rfc1123 hostname recognized as "bad")

Your message dated Mon, 5 Feb 2018 12:31:22 +0100
with message-id <8f408e70-abeb-ce71-94e2-9e17a1cb2520@debian.org>
and subject line Re: Bug#789475: udhcpc: valid rfc1123 hostname recognized as "bad"
has caused the Debian Bug report #789475,
regarding udhcpc: valid rfc1123 hostname recognized as "bad"
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.)


-- 
789475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789475
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: busybox
Version: 1:1.22.0-9+deb8u1
Severity: normal
Tags: d-i

Dear Maintainer,

The valid hostname "52-54-0-12-34-56" is recognized as bad while it should be valid according to rfc1123 (Section 2.1).

-----
Capture of the DHCP reply:
    be1.lrz.bootps > 192.168.7.107.bootpc: BOOTP/DHCP, Reply, length 300, xid 0x4cc35164, Flags [none]
          Client-IP 192.168.7.107
          Your-IP 192.168.7.107
          Client-Ethernet-Address 52:54:00:12:34:56 (oui Unknown)
          file "be1"
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: ACK
            Server-ID Option 54, length 4: be1.lrz
            Lease-Time Option 51, length 4: 600
            Subnet-Mask Option 1, length 4: 255.255.255.0
            Default-Gateway Option 3, length 4: be2.lrz
            Domain-Name-Server Option 6, length 4: be1.lrz
            Hostname Option 12, length 16: "52-54-0-12-34-56"
            Domain-Name Option 15, length 3: "lrz"


-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages busybox depends on:
ii  libc6  2.19-18

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1:1.27.2-1

On 30/01/17 17:33, Thorsten Glaser wrote:
> Hi,
> 
> I’ve stumbled upon this bug by means of d-i using “bad” as hostname
> right now as well and tracked it down to the offending piece of code
> myself.
> 
> When reading the bugreport messages, I found out that the patch linked –
> https://git.busybox.net/busybox/patch/?id=c29021e2a594fb29471c8c7e61ab8f45296622ba
> – is indeed correct and will fix this issue.

That commit was included in the Busybox 1.24.0 upstream release, and
therefore included in the Debian upload for 1:1.27.2-1 back in September.

Regards,
Chris

-- 
Chris Boot
bootc@debian.org

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: