Description of problem: When running a LiveCD, there are no firewall rules configured. This is a big security risk because there are services listening on network sockets by default. There really should be a default set of firewall rules in /etc/sysconfig/iptables and /etc/sysconfig/ip6tables for the LiveCD case. Version-Release number of selected component (if applicable): F10-Snap2 Additional info: Inet sockets that are bound on LiveCD: udp 0 0 0.0.0.0:68 0.0.0.0:* 3086/dhclient tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2728/rpcbind udp 0 0 0.0.0.0:111 0.0.0.0:* 2728/rpcbind udp 0 0 0.0.0.0:631 0.0.0.0:* 3156/cupsd udp 0 0 0.0.0.0:779 0.0.0.0:* 2728/rpcbind udp 0 0 0.0.0.0:799 0.0.0.0:* 2743/rpc.statd udp 0 0 0.0.0.0:5353 0.0.0.0:* 3118/avahi-daemon: udp 0 0 0.0.0.0:33846 0.0.0.0:* 3118/avahi-daemon: tcp 0 0 0.0.0.0:36319 0.0.0.0:* LISTEN 2743/rpc.statd udp 0 0 0.0.0.0:50943 0.0.0.0:* 2743/rpc.statd
Hmm, apparently we've been doing this all the way since the initial live images for Fedora Core 6 were built. I'm a little bit wary of changing things such that there's a firewall running with this little time left in the F10 cycle :-/
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
IIRC I noticed that this has been solved in Fedora 11, probably by fedora-live-base.ks having "firewall --enabled --service=mdns"