Firewalld

[Leslie S Satenstein]

Hi Pete

In my view, Firewalld write-up belongs in the security guide. Have a reference in the  system admin guide that points to the Security guide for Firewalld.

Security includes networking, programming concerns, Networking and non Linux activities, Security documentation should be considered as a bible.  Everything in it is a "Need To Know". Firewalld setup is a Need to Know ability. 


As an aside, our local university provides a Masters degree in CS with all aspects of IT security.  When you complete this MSc degree in security, you can work for the highest government levels in Canada and of course, in the USA or elsewhere. 



 
Regards 

 Leslie

Mr. Leslie Satenstein
SENT FROM MY OPEN SOURCE LINUX SYSTEM.




>________________________________
> From: Pete Travis <lists at petetravis.com>
>To: For participants of the Documentation Project <docs at lists.fedoraproject.org>; Eric H. Christensen <sparks at fedoraproject.org>; Stephen Wadeley <swadeley at redhat.com> 
>Cc: For participants of the Documentation Project <docs at lists.fedoraproject.org> 
>Sent: Monday, August 25, 2014 3:13 PM
>Subject: Firewalld
> 
>
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>So, I was working on some firewalld rules today, and encountered
>situations we haven't documented, as well as some new features we
>haven't covered.  It got me thinking about the way we document
>firewalls; some things in the Security Guide, some allusions in the
>Networking Guide or Sysadmin Guide, some missing.  I think that a
>general overview of firewalld and basic usage is appropriate in all of
>these places, but I don't like the omission when a book gets down to
>specifics.
>
>So, which Guide should provide indepth coverage of the firewall? Eric
>and Stephen, fight!
>
>Here's my idea:  In the security guide, give an overview, instructions
>on how to lock down to deny-all, general instructions on adding back,
>and link out to the Networking Guide. In the NG, give a full overview -
>network security should be an inherent part of network configuration. 
>In others, include the command to open a port for the service being
>documented where appropriate.
>
>- -- 
>- -- Pete Travis
>- Fedora Docs Project Leader
>- 'randomuser' on freenode
>- immanetize at fedoraproject.org we havent covered
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1
>
>iQEcBAEBAgAGBQJT+4rqAAoJEL1wZM0+jj2ZAE4H/jxg3qdrZ08ioLM3W8T+Ubsn
>Rvfaq5nawBLjtc/xvwX4awjtZRDLgfugoxQnDb4gog0W1/f1BrZ6+fs6qvAAxtKb
>oIXE4QCegLsva1c4LfAPE/DCxqFiFWGK65jdXD3dytx/I+Y9xCEYpMR/huLwApiL
>zN7hZ+OUgfNswLRowPcqCPmPFWFJOefnDB7wNPh/heChXZ2MM2lLKa41TabaPYfw
>Rgi8/5RwJR+6BVs2aG72dgP9gIZ6EmPIanKr95/4Tpd6xsBYwgL1wvPqIAn+KXUe
>INwpXLu1iVIL3s99R1kZdIdoPP2wHOv2y31YabuAKUEVr9MIizLjIsGQ+k1OXFM=
>=8Zi9
>-----END PGP SIGNATURE-----
>
>-- 
>docs mailing list
>docs at lists.fedoraproject.org
>To unsubscribe:
>https://admin.fedoraproject.org/mailman/listinfo/docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/docs/attachments/20140825/d3a4f34a/attachment.html>