Bug 97029 - redhat-config-network resets passwords in /etc/ppp/chap-secrets
redhat-config-network resets passwords in /etc/ppp/chap-secrets
Status: CLOSED DUPLICATE of bug 97027
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-06-09 08:15 EDT by bastiaan
Modified: 2007-04-18 12:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:56:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bastiaan 2003-06-09 08:15:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
If you edit any network device and save the settings (via 'File/Save')
redhat-config-network will reset the passwords of all entries in
/etc/ppp/chap-secrets to the value "None".
It does not matter whether the modified network device is a PPP / CHAP
connection or not.


Version-Release number of selected component (if applicable):
redhat-config-network-1.2.3-3

How reproducible:
Always

Steps to Reproduce:
1. create a PPP based network device, e.g. xDSL, and save the settings
2. edit any of the available network devices, and save the settings

    

Actual Results:  The password of the PPP device in /etc/ppp/chap-secrets has
been reset to "None"

Expected Results:  The password should have kept the original value. 

Additional info:

I'm not sure whether having a default password "None" may pose a security risk,
but to be safe I set the severity of this bug to 'security'.
Comment 1 Harald Hoyer 2003-06-10 11:18:06 EDT

*** This bug has been marked as a duplicate of 97027 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:56:38 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.