|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 HTTP Module does not identify http and https services correctly. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | John Shand <jshand2013> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | jreidinger, kanderssen, matthias.gerstner, mchandras |
| Version: | Current | Flags: | kanderssen:
needinfo?
(mchandras) |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
John Shand
2018-01-28 23:44:41 UTC
knut can you please check it, if it is result of firewalld transformation? For SuSEFirewall2 apache2 was providing the definition of the service. As the yast2-http-server module modifies the definition of the service we were thinking in continue providing it by the apache2 package as apache2 and apache2-ssl. So will request the opinion of the firewalld maintainer and from the security team. In general we adapted our modules using the firewalld defined services when not touched by YaST, but deployed the services definition when touched, but of course that could create doubts about both services (http and apache2). This bug can be considered a duplicate of 1076837. So please, continue the discussion there. *** This bug has been marked as a duplicate of bug 1076837 *** I will answer this in bug 1071548. |