Bug 22978 - kernel-pcmcia-cs / network
Summary: kernel-pcmcia-cs / network
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: hotplug
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Brock Organ
URL:
Whiteboard: Florence Gold
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-29 10:48 UTC by Gerald Teschl
Modified: 2007-04-18 16:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-02 22:40:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Gerald Teschl 2000-12-29 10:48:08 UTC
A pcmcia network card will be brought up even if network is stopped!
This could impose a security risk if one starts into runlevel 1 and
starts pcmcia to access say a pcmcia cdrom. Then the network card
will be started unintentionally as well (without ipchains/iptables
started!)

The following patch should do the trick, but for some reason the card
is still brought up (even if you rm /etc/pcmcia/network)!?


--- network.orig        Fri Dec 29 11:34:13 2000
+++ network     Fri Dec 29 11:44:18 2000
@@ -13,7 +13,10 @@
 
 case "${action:?}" in
 'start')
-       /etc/sysconfig/network-scripts/ifup ifcfg-${device}
+       if [ -f /var/lock/subsys/network ]
+       then
+               /etc/sysconfig/network-scripts/ifup ifcfg-${device}
+       fi
     ;;
 'stop')
        /etc/sysconfig/network-scripts/ifdown ifcfg-${device}

Comment 1 Glen Foster 2001-01-11 21:03:59 UTC
This defect is considered MUST-FIX for Florence Gold release

Comment 2 Erik Troan 2001-03-01 02:28:52 UTC
bill, should we change this? w/ the new hotplug stuff it's a larger question

Comment 3 Bill Nottingham 2001-03-01 02:31:11 UTC
We should probably change that in hotplug, yes.

Comment 4 Trond Eivind Glomsrxd 2001-03-02 22:39:24 UTC
Should be fixed in hotplug-2001_02_14-12. Try them at http://people.redhat.com/teg/

Comment 5 Trond Eivind Glomsrxd 2001-03-02 22:40:00 UTC
(which you definitely should use on a much newer beta...)


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