On Tue, 2005-11-29 at 16:11 +0000, D. D. Brierton wrote:
> $ cat /etc/sysconfig/system-config-securitylevel
> # Configuration file for system-config-securitylevel
>
> --enabled
> --port=6881:tcp
> --port=6882:tcp
> --port=6883:tcp
> --port=6884:tcp
> --port=6885:tcp
> --port=6886:tcp
> --port=6887:tcp
> --port=6888:tcp
> --port=6889:tcp
>
> So, is system-config-securitylevel busted?
I think I've found out what the problem was. system-config-securitylevel
isn't busted, but does perhaps have a subtler issue. When I upgraded to
FC4 I did a clean install and then merged in parts of my FC3 /etc. One
of the things I did was to copy my
old /etc/sysconfig/system-config-securitylevel over. I then started
system-config-securitylevel to make sure it had picked up those settings
and clicked okay, assuming the new rules would be written into my
iptables file. That last assumption is false, because as far as
system-config-securitylevel was concerned I hadn't changed anything.
I remedied the problem by starting system-config-securitylevel again,
editing out the last port, and then clicking okay and lo and behold my
iptables rules were updated. Obviously it was then trivial to add the
last port back again.
I'm really posting this just in case someone else might have made the
false assumption I did.
Best, Darren
--
=====================================================================
D. D. Brierton darren@xxxxxxxxxxx www.dzr-web.com
Trying is the first step towards failure (Homer Simpson)
=====================================================================
