Checkup
by Mike McGrath
Hey guys, so we still don't have any 'finished' books but I thought I'd
check in to see what you all think about the format of the thing by now.
I'm a really big fan of the checklist stuff we're doing in some of the
standards but cross checklisting has become a concern of mine. I've been
re-thinking the view here and am starting to wonder if we should focus
more on the audience and less on the technology. For example, while
writing the end user security policy I wanted to reference some of the
information in the openssh book.
The problem I'm running into is keep it modular but also in a way that
makes sense. I looked at including sections in one book in another and
got an error, there may be a way to overcome that, not sure. What are
your thoughts?
-Mike
15 years, 7 months
Iptables standards and configuration management
by Stephen John Smoogen
One of the items that I have to deal with at UNM is a long list of
different firewalls and servers. I have Solaris(9,10), AIX(various),
MacOSX(various), and SuSE(various), RHEL(2,3,4,5), and Fedora(7,8,9)
to worry about with lots of different firewall needs for each one. As
I am trying to standardize the firewalls... I run into that same
headache everyone runs into at some point or another... How does one
organize the various different firewalls in both the VCS and the
upcoming configuration management system... while perfect is the enemy
of the good.. what is a good way of doing it as I see way to many ways
of laying it out in file structure.
firewalls/project/OS/system
project/firewall/OS/system
OS/firewall/project/system
OS/system/project/firewall
etc etc etc. with some other // items added. Any ideas?
--
Stephen J Smoogen. -- BSD/GNU/Linux
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"
15 years, 8 months