|
Bugzilla – Full Text Bug Listing |
| Summary: | firewall enabled by default: modify network settings in 1st stage | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Jiří Suchomel <jsuchome> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | coolo, locilka, security-team |
| Version: | Alpha 3plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| See Also: | https://fate.suse.com/303859 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jiří Suchomel
2008-04-11 13:41:44 UTC
it's not a big problem, but I'm afraid of your "at least", because I think it would open a never ending flood of second stage features coming in. So I would like to wait for beta1 feedback, before I give green light. I wonder how hard it is though, the users in first stage caused quite some effort, no? (In reply to comment #1 from Stephan Kulow) > I wonder how hard it is though, the users in first stage caused quite some > effort, no? Yes, but saving one boolean value would be a different thing. But it is true that than someone might want full network setup in the 1st stage... I know that it was actually the security teams's biggest concern that people will hate the default firewall even more if they are unable to disable it easily. Would this be ok to PM? from a security point of view, its fine to have a "firewall: yes/no" question in 1st stage. there have not been that many complaints about the default firewall yet however. I don't have any objections either for this to go in if Michal's time allows. But please make sure that we don't pull the whole firewall/network stack into first stage. It really has to be a minimal client Minimal network client - can we re-use that dropped one (used for set up network for additional repos in 1.st stage)? It's not a 'dropped one', we still have and use it. inst_network_check.ycp + inst_network_setup.ycp And of course, the network setup is very different to anything used in second stage. Also writing a firewall isn't prepared for such a feature (write only?). IMHO the implementation of this feature could be very simple: just writing somewhere (Directory::vardir) the information if firewall should be enabled or disabled. During the second stage, such information is read anyway by network configuration ("enable_firewall" in control.xml), the only added part here would be that if there exist some saved value from first stage, it would serve as a new default instead of the one found in control file.
Sorry, I don't have time for that now mass reopening of later+remind bugs of 11.0 Closed, it's feature in FaTE |