Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 97029

Summary: redhat-config-network resets passwords in /etc/ppp/chap-secrets
Product: [Retired] Red Hat Linux Reporter: bastiaan
Component: redhat-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9Keywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:56:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description bastiaan 2003-06-09 12:15:47 UTC
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 15:18:06 UTC

*** This bug has been marked as a duplicate of 97027 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:56:38 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.