Bug 80369 - SECURITY: WEP key value world readable
SECURITY: WEP key value world readable
Status: CLOSED DUPLICATE of bug 73850
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Brock Organ
: Security
Depends On:
  Show dependency treegraph
Reported: 2002-12-24 23:47 EST by Robert de Rooy
Modified: 2008-01-17 12:49 EST (History)
4 users (show)

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

Attachments (Terms of Use)

  None (edit)
Description Robert de Rooy 2002-12-24 23:47:19 EST
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:

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

Additional info:
Comment 1 Mike McLean 2003-01-02 15:26:46 EST

*** This bug has been marked as a duplicate of 73850 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:34 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.