Bare bones is fine, but you miss out on the tools which may make your life
easier. As an example you can configure a DB (PostgreSQL, mySQL, whatever)
using the command, but it is frequently more time-cost effective to use a
tool.
Things like SSH used to be optional at one time. Now it is in every
Le 13/10/2014 13:36, Ron Loftin a écrit :
Of course, if you are interested in something that will help you to
organize your rules, there is always Shorewall ( Shoreline Firewall )
which I have used for years and found very effective and time-saving.
Thanks for the suggestion, I'll look into it.
On Mon, 2014-10-13 at 12:30 +0200, Niki Kovacs wrote:
> Le 13/10/2014 11:11, Reindl Harald a écrit :
> > just write a bash script which resets and configures iptables with the
> > "iptables" command and at the end of the script call "/sbin/service
> > iptables save" which writes the current rules
Le 13/10/2014 11:11, Reindl Harald a écrit :
just write a bash script which resets and configures iptables with the
"iptables" command and at the end of the script call "/sbin/service
iptables save" which writes the current rules to /etc/sysconfig/iptables
and so at boot the rules get loaded atom
Hi,
I'm planning to use CentOS 6.x on a handful of LAN servers. So far I've
been using Slackware64 14.0 and 14.1 for the job.
I wonder what's the orthodox/recommended way of configuring and iptables
firewall with CentOS. I understand there's the
system-config-securitylevel-tui NCurses interf
5 matches
Mail list logo