/sbin/dhclient-script has bashisms
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | isc-dhcp (Ubuntu) |
High
|
Unassigned | ||
Bug Description
/sbin/dhclient-
root@mystic:~# ifup br0
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https:/
Listening on LPF/br0/
Sending on LPF/br0/
Sending on Socket/fallback
DHCPREQUEST of 172.31.3.6 on br0 to 255.255.255.255 port 67 (xid=0x7488da46)
DHCPACK of 172.31.3.6 from 172.31.3.4
RTNETLINK answers: File exists
bound to 172.31.3.6 -- renewal in 38988 seconds.
/sbin/dhclient-
/sbin/dhclient-
/sbin/dhclient-
/sbin/dhclient-
root@mystic:~# head -n1 /sbin/dhclient-
#!/bin/sh
root@mystic:~#
Shebang line needs to be /bin/bash, or the script needs to be rewritten.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: isc-dhcp-client 4.3.1-5ubuntu2
ProcVersionSign
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Sun Apr 26 10:29:56 2015
EcryptfsInUse: Yes
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago)
| Kevin Otte (nivex) wrote : | #1 |
| Changed in isc-dhcp (Ubuntu): | |
| importance: | Undecided → Low |
| Thomas Ward (teward) wrote : | #3 |
Note that because of the Bashisms whatever address was negotiated is not assigned. This applies at least to IPv6, and if the bashisms interfere in IPv4 then it also interferes there.
This means the essential function of the application does not operate, and the bug should potentially be a higher severity level. (I'm setting to High because it "renders essential features or functionality of the application or dependencies broken or ineffective" - which is defined as a "High" criterion in the Bug Importance page of the bugsquad documentation)
| Changed in isc-dhcp (Ubuntu): | |
| importance: | Low → High |


Status changed to 'Confirmed' because the bug affects multiple users.