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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
That is a very hard to answer question because I would have to know all the gory details of security architecture wrt SELinux, LIDS, RSBAC, GRSecurity and whatnot (I don't). You could twist my arm and I'd say that I guess RSBAC is similar to SELinux, but the last one has finer grained controls, allows dynamic policy changes and much more. Both RSBAC and SELinux allow much finer grained controls compared to GRSecurity, and that comes at a price, making GRSEC is easier to set up for Linux newbies with not much security admin knowledge (depending on your skills ofcourse).
I think Gentoo deserves credit here, being the only distro I know of that offers prebuilt kernels for LIDS, RSBAC and GRSecurity, which would make it much easier for ppl who like to see what different security architectures are like to work with.
Thank you. Correct me if I am wrong. I have read that RSBAC is much better in terms of security in comparison to GRSecurity. Also my understanding from what you wrote "Both RSBAC and SELinux allow much finer grained controls compared to GRSecurity, and that comes at a price, making GRSEC is easier to set up for Linux newbies with not much security admin knowledge" that GRSecurity is much easier to setup than RSBAC. However is it enough or would it suffice? Who would use RSBAC in place of GRSecurity?
However is it enough or would it suffice?
I don't know how to define "enough" in this case. I'd say it depends on your needs and knowledge. If you're a newbie setting up your first SOHO webserver of shellserver I'd say GRSecurity would be a good start (next to other security measures ofcourse). If you're responsable for a network running applications that for instance do complex financial transactions, you'll want something more "advanced", some form of Orange Book compliance.
*BTW Markus, one of our forum members, brought to my attention bad news GRSecurity might not live long. Seems Spender, the main developer, is out of funds cuz one of GRSecurity's sponsors didn't fulfill their promises. If it turns out that way, it definately is sad news.
Thank you for clearing that up for me. In reference to Markus's news, what would happen should anyone use GRSecurity and it is no longer continued? What are the risks? Digressing, how was GRSecurity being sponsored?
what would happen should anyone use GRSecurity and it is no longer continued?
For the current situation: nothing. Once new kernel minor versions are released and people can still patch it: nothing. For 2.6.x: choose something else. AFAIK LSM and GRSEC aren't playing nice together. I'm going to keep patching my 2.4.x boxen until GRSEC breaks, but eventually I'll move to SELinux.
What are the risks?
You mean risks like in GRSEC breaking stuff or coming up with new ways to attack a system?
Digressing, how was GRSecurity being sponsored?
"Badly" probably describes the situation the best :-[