Bug 1292926
| Summary: | firewalld --new-service & malformed xml ?? | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | lejeczek <peljasz> |
| Component: | firewalld | Assignee: | Thomas Woerner <twoerner> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Kepler <jkejda> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | jkejda, todoleza |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | firewalld-0.4.2-1.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-03 21:02:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
lejeczek
2015-12-18 18:49:55 UTC
--new-service creates a new service, but is not using a local file for this. This would be very good to add, though. I think about --new-service-from-file=<file> or --new-service=<name> --file=<file> I see.. Yes, it would be very useful indeed to be able to use prepped file. also, if I may, --service-info which could dump whole lot about service would be nice too. and would it great not to have to reload the daemon to see this newly added service. I've just come across something, I've tried man pages but could not find any info on '&' char. And it seems that if it is in .xml file (I had in <description>) then firewalld omits silently. The ampersand is a special character in XML: https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references If you are writing into an XML file, you need to take care about the syntax. yes, but this - if one makes one mistake in one .xml then the rest, if there are other custom services xmls, get silently skipped! Services are there listed as attached to zones but ports are not opened! test it - make a mistake in <port> eg. put 443,444 instead of 443-444 (and I imagine many of us will be makeing it, old iptables style habit) and all custom services are affected. I'd be nice to have firewalld resilient to this. (In reply to lejeczek from comment #9) > yes, but this - if one makes one mistake in one .xml then the rest, if there > are other custom services xmls, get silently skipped! Services are there > listed as attached to zones but ports are not opened! > Please open an extra bug for this - it is a different issue. Fixed upstream: https://github.com/t-woerner/firewalld/commit/35802812f374f8075c07cae672e150069ea6117a https://github.com/t-woerner/firewalld/commit/6df8dfa079817ef4c60388b45679426ed5bea2cd Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2597.html |