Bug 1399500 - Use "service iptables save" consistently
Summary: Use "service iptables save" consistently
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Zac Dover
QA Contact: Lucie Jirakova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 08:25 UTC by Stephen Wadeley
Modified: 2019-09-26 14:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-11 00:45:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Stephen Wadeley 2016-11-29 08:25:04 UTC
Document URL: 
https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-2-preparing-your-environment-for-installation

Section Number and Name: 
2.6. Enabling Connections from a Client to Satellite Server
2.7. Enabling Connections from Capsule Server to Satellite Server
2.8. Enabling Connections from Satellite Server and Clients to a Capsule Server
5.2. Verifying and Starting the DNS Service
5.4. Configuring Satellite Server with External DHCP
5.6.1. Configuring the Firewall for External Access to TFTP

Describe the issue:

This command:
iptables-save > /etc/sysconfig/iptables

 is not as safe to use as:
service iptables save

1] Partly because we avoid the use of redirection in commands  because they are not as safe or newbie friendly as other methods

2] It is possible to change the path in the config file, which would make that command not work but the "service iptables save" command would still work.

Suggestions for improvement:

sed -i "s|iptables-save > /etc/sysconfig/iptables|service iptables save|g" topics/*.adoc

Additional information:

Comment 2 Andrew Dahms 2017-01-10 12:15:18 UTC
Assigning Lucie as the QA contact.

Lucie - can you take a look at the changes for this bug?

Comment 4 Andrew Dahms 2017-01-11 00:45:01 UTC
This content is live on the Customer Portal.

Closing.


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