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

Bug#695121: marked as done (kppp not resolvconf-aware; appears to clobber /etc/resolvconf)



Your message dated Thu, 22 Aug 2019 01:47:16 +0000
with message-id <[🔎] E1i0cC4-0004mF-4s@fasolo.debian.org>
and subject line Bug#935232: Removed package(s) from unstable
has caused the Debian Bug report #695121,
regarding kppp not resolvconf-aware; appears to clobber /etc/resolvconf
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.)


-- 
695121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695121
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kppp
Version: 4.8.4-1
Severity: important

Looking at the kdenetwork 4.8.4-1 source code I see the following code snippets in kppp/connect.cpp starting at line 1419:

    // Replace the DNS domain entry in the /etc/resolv.conf file and
    // disable the nameserver entries if option is enabled
    void add_domain(const QString &domain) {

    // adds the DNS entries in the /etc/resolv.conf file
    void adddns()
    {

    // remove the dns entries from the /etc/resolv.conf file
    void removedns() {

The code inside the functions writes directly to /etc/resolv.conf. Nowhere is there a check for the presence of /sbin/resolvconf.

When /sbin/resolvconf is present and executable it is not permitted to write directly to /etc/resolv.conf. Programs that want to make changes to resolv.conf must interface with /sbin/resolvconf which takes care of adding material to and removing material from resolv.conf. Please see /usr/share/doc/resolvconf/README.gz for more instructions.

It looks as if kppp writes to /etc/resolv.conf and does not mv /etc/resolv.conf. So if /etc/resolv.conf is a symbolic link, as is normally the case when resolvconf is installed, then kppp will write through the link to /run/resolvconf/resolv.conf. Then the next time resolvconf updates this file, kppp's changes will be obliterated.

I haven't tested kppp so I don't know whether the code in question is actually executed.

--- End Message ---
--- Begin Message ---
Version: 4:17.08.3-1+rm

Dear submitter,

as the package kppp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935232

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply to: