Your message dated Thu, 17 Feb 2005 19:17:31 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295315: fixed in pppoeconf 1.1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Feb 2005 23:38:59 +0000
>From [EMAIL PROTECTED] Mon Feb 14 15:38:59 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp1.wanadoo.fr [193.252.22.30] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1D0pnv-0001Kw-00; Mon, 14 Feb 2005 15:38:59 -0800
Received: from me-wanadoo.net (localhost [127.0.0.1])
        by mwinf0103.wanadoo.fr (SMTP Server) with ESMTP id EEF191F92690;
        Tue, 15 Feb 2005 00:38:27 +0100 (CET)
Received: from stellie.bailly.home (ANantes-201-1-34-102.w81-53.abo.wanadoo.fr 
[81.53.166.102])
        by mwinf0103.wanadoo.fr (SMTP Server) with ESMTP id C6B551F92684;
        Tue, 15 Feb 2005 00:38:27 +0100 (CET)
X-ME-UUID: [EMAIL PROTECTED]
Received: from leo by stellie.bailly.home with local (Exim 4.34)
        id 1D0pnQ-000414-Fx; Tue, 15 Feb 2005 00:38:28 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Leopold BAILLY <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: pppoeconf: sed command fails when user contains a / character
X-Mailer: reportbug 3.2
Date: Tue, 15 Feb 2005 00:38:28 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: pppoeconf
Version: 1.0.11
Severity: critical
Justification: causes serious data loss

When updating chap-secrets and pap-secrets, pppoeconf uses a sed command that 
fails if the user string contains a / character.
The consequence is that all previous content of these files is lost.
Wanadoo, a french ISP, has given to me such a user name.

The use of "grep -v" should be more appropriate.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages pppoeconf depends on:
ii  ppp                     2.4.2+20040428-5 Point-to-Point Protocol (PPP) daem
ii  whiptail [whiptail-prov 0.51.6-20        Displays user-friendly dialog boxe

-- no debconf information


---------------------------------------
Received: (at 295315-close) by bugs.debian.org; 18 Feb 2005 00:23:01 +0000
>From [EMAIL PROTECTED] Thu Feb 17 16:23:01 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1D1vvB-0005b8-00; Thu, 17 Feb 2005 16:23:01 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1D1vpr-0004k8-00; Thu, 17 Feb 2005 19:17:31 -0500
From: Eduard Bloch <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#295315: fixed in pppoeconf 1.1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 17 Feb 2005 19:17:31 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 2

Source: pppoeconf
Source-Version: 1.1

We believe that the bug you reported is fixed in the latest version of
pppoeconf, which is due to be installed in the Debian FTP archive:

pppoeconf_1.1.dsc
  to pool/main/p/pppoeconf/pppoeconf_1.1.dsc
pppoeconf_1.1.tar.gz
  to pool/main/p/pppoeconf/pppoeconf_1.1.tar.gz
pppoeconf_1.1_all.deb
  to pool/main/p/pppoeconf/pppoeconf_1.1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Eduard Bloch <[EMAIL PROTECTED]> (supplier of updated pppoeconf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 18 Feb 2005 01:07:21 +0100
Source: pppoeconf
Binary: pppoeconf
Architecture: source all
Version: 1.1
Distribution: unstable
Urgency: high
Maintainer: Eduard Bloch <[EMAIL PROTECTED]>
Changed-By: Eduard Bloch <[EMAIL PROTECTED]>
Description: 
 pppoeconf  - configures PPPoE/ADSL connections
Closes: 291865 295315
Changes: 
 pppoeconf (1.1) unstable; urgency=high
 .
   * do not stumble over PPP usernames with slashes within (closes: #295315)
   * minor English language bugs fixed (closes: #291865)
Files: 
 643481bf7a3256d49782ac4bfc995552 518 net optional pppoeconf_1.1.dsc
 1f7ed1eda5072449ab629a08354a27dd 41902 net optional pppoeconf_1.1.tar.gz
 2e47d0a0668f5ee5bae913461078b21a 39222 net optional pppoeconf_1.1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCFTL24QZIHu3wCMURAhpjAJwJA4/QkyLwglaQPFSC72zCq8LR1ACfQvQ/
qhboZuDvDrpKhAMaoxFoM4k=
=gABW
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to