documentation and programming follows resolvconf

Bug #896734 reported by jb
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openresolv (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

If one has
 dns-nameservers 192.168.1.2
 dns-search localdomain

in their /etc/network/interfaces (set ifupdown(managed is false) and keyfile(ignore mac address) sections for /etc/Networkmanager/Networkmanager.conf)

cat /etc/resolvconf.conf -->
"
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1
"

cat /etc/NetworkManager/NetworkManager.conf -->
"

[main]
plugins=ifupdown,keyfile

[keyfile]
unmanaged-devices=mac:00:24:1d:c6:e6:19;mac:00:50:b6:06:c9:f1;mac:00:50:b6:06:c3:99

[ifupdown]
managed=false
"

cat /etc/network/interfaces -->
"
auto lo
iface lo inet loopback

allow-auto eth1 eth2
allow-hotplug eth2 eth1

iface eth1 inet static
 address 10.253.253.2
 netmask 255.255.255.0
 broadcast 10.253.253.255

iface eth2 inet static
 address 192.168.1.83
 netmask 255.255.255.0
 broadcast 192.168.1.255
 gateway 192.168.1.1
 dns-nameservers 192.168.1.2
 dns-search localdomain
..

you see,
  dns-nameservers 192.168.1.2
 dns-search localdomain

is meant to work with the resolvconf package.
nowhere does it these two stanzas are mentioned in the openresolv manual
these two stanzas are meant to be used by the resolvconf package (resolvconf is not my system)

your if-up.d/000resolvconf
"
printf "$conf" | /sbin/resolvconf -a "$IFACE.$ADDRFAM"
"
the -a paramater to resolvconf is what is parsing this..

..However.. I tried the interfaces file without these two stanzas, and instead tried to use
name_servers=192.168.1.2
, then applied /etc/networking restart ..
Does not work.. but if I apply manually "openresolv -u", /etc/resolvconf.conf then gets parsed to include 192.168.1.2

I find using the two stanzas in /etc/network/interfaces much more elegant as a solution, and would like to know if openresolv was meant to be used this way or if it actually is a bug of having old-codebase from openresolv.

I hope you can take a look at this soon so I can post this/(or to later to revise) solution on having NetworkManager.conf/interfaces file setup.. (I dont want to post a solution for interfaces knowing an update may force users to then setup /etc/resolvconf.conf) Thanks..

 -- I also believe this may a security vulnerability.. If a program can operate in a way outside the context of it's documentation, then I believe malicious commands can be placed outside of its expected configuration..

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: openresolv 3.4.0-1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Nov 26 19:27:33 2011
Dependencies:

InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
SourcePackage: openresolv
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
jb (jagginess) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
security vulnerability: yes → no
visibility: private → public
visibility: private → public
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in openresolv (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openresolv (Ubuntu) because there has been no activity for 60 days.]

Changed in openresolv (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.