Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I know next to nothing about all of this. I've been using Fedora Core 4. Does this OS require additional firewall, security software or do I need to activate provided software to insure my computer isn't vulnerable to invasion etc? Or is that all installed when you install the OS? Just wondering as this isn't obvious from looking at the desktop etc. I have a ethernet connection to a Netgear Rangemax router.
It comes with iptables firewall and SELinux. Both of which deal with security. SELinux has lousy documentation so most people turn don't turn it on. iptables allows for firewall configuration but doesn't have much enabled by default normally. There is apparently a GUI frontend called Firestarter. I don't use the GUI much so can't say whether it comes with FC4 or not.
In addition to firewall it is normal to disable services that open ports if you don't use them. (e.g. telnetd and ftpd usually are disabled by default but can be enabled - you shouldn't enable them without a specific need. using ssh and scp/sftp is preferred as those are more secure).
Last edited by MensaWater; 01-29-2007 at 09:21 AM.
I, personally, only follow some of his recommendations. In particular, like jlightner, I'm rather fond of ssh. And though I'm probably in the minority, I actually like bluetooth for some things too, so keep those services enabled. Oh, and on my WiFi laptop I always enable NetworkManager. But anyway, opinions on what's "best practice" vary considerably, so you'll have to evaluate the risk/reward of each based on your own particular needs.
If you want to understand SELinux there is nothing that beats dead trees. Sorry. I currently have on my desk Prentice Hall's "SELinux by Example" by Mayer, Macmillan and Caplan (which I still have to write a review for) and it's what you want, believe me. It explains how it's structured, has good examples and explains to write and modify policies.
If you just want to use SELinux then the first thing I'd notice is how much FC6 differs from FC5 (note I usually don't do distro talk trying to be as distro-agnostic as I can and I have *no* idea of RHEL5). With the disappearance of separate SELinux policy sources (the ones which you had to D/L separately from Tresys) and using tools like semanage with audit2allow FC6 *really* makes it easier. That is not to say there are no problems at all, like Setroubleshootd keep saying to chcon something, but it's definately easier, way more usable. But I don't know how much in-depth nfo the FC site and Wiki have on SELinux.