Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 80369

Summary: SECURITY: WEP key value world readable
Product: [Retired] Red Hat Linux Reporter: Robert de Rooy <rderooy>
Component: redhat-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: chris.ricker, mitr, notting, wtogami
Target Milestone: ---Keywords: Security
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:50:34 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 Robert de Rooy 2002-12-25 04:47:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
I'm not sure under which component this bug belongs, but I guess
/etc/sysconfig/network-scripts/* would fall under initscripts. Sorry if that is
not the case.

This bug effects both RH8.0 and phoebe.

When configuring a wireless network adapter using redhat-config-network it asks
for such values as the ESSID and secret WEP KEY
The problem is that the KEY gets written to the respective ifcfg-eth* file as a
key= value and this file is readable to every user on the system.

e.g. on my system eth1 is my wireless adapter, and the file
/etc/sysconfig/network-scripts/ifcfg-eth1 has the following permissions:
-rw-r--r--    3 root     root          298 Dec 23 22:25 ifcfg-eth1


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.setup wireless networking with WEP enabled
2.
3.
    

Additional info:

Comment 1 Mike McLean 2003-01-02 20:26:46 UTC

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

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