Bug 177735 - can't enable firewall within installer
Summary: can't enable firewall within installer
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2006-01-13 16:52 UTC by Alexandre Oliva
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2006-01-13 18:17:39 UTC

Attachments (Terms of Use)

Description Alexandre Oliva 2006-01-13 16:52:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8) Gecko/20060103 Fedora/1.5-4 Firefox/1.5

Description of problem:
I dispute the wisdom of enabling boxes to be installed and booted up before the firewall can be set up in firstboot.  I can see that in some cases this might be what you want, but most often you should boot the box up already secure the first time.

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

How reproducible:

Steps to Reproduce:
1.Install (no question asked about firewall or selinux any more)
2.Boot system up
3.Leave firstboot run unattended

Actual Results:  You have a number of services running without anything to protect them until you get to answer the firstboot prompt.

Expected Results:  Machine should be safe when it first boots up.

Additional info:

Comment 1 Chris Lumens 2006-01-13 18:17:39 UTC
When anaconda is done, you have SELinux set in enforcing mode and basically all
ports but SSH closed.  I say basically all because CUPS and mDNS are also open,
though you can't close those no matter what you do with the current
implementation of system-config-securitylevel (I have plans to fix that). 
firstboot is really only giving you the opportunity to open more stuff up, as
the defaults are pretty strict now.

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