Looking for opinions: Best stack protection for Linux?
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Looking for opinions: Best stack protection for Linux?
I know of several options for kernel protection on Linux, such as PAX, openwall, and grsecurity that includes PAX, but does anyone have practical experience comparing the different patches available and what their effectiveness and performance impact is? Specifically I'm looking for something that would work with a 2.6 kernel on Fedora. I don't actually have a Fedora box of my own to test with, but I'm trying to select a solution to use for a production quality software product. I'm not terribly interested in grsec because it looks like it would have a pretty huge impact on the system and might cause us a lot of debugging to get everything running smoothly.
I'm really interested in hearing from people who have actually applied them to systems.
my experience with grsec has been rather ok (first time i set it up i accidentally turned on one of the security options, that caused xdm to randomly not do its job (i for get, did it crash, or did it randomly just not do its stuff after someone logged off)
anyways, I'm on a athlon 2600 to i don't think i would see a performance hit, altho i do have it setup to log almost everything (even exec ... geez i got really really long logs), just be careful and read the help for every option because they can break some programs ....
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Original Poster
Rep:
That's really why I wanted to stay away from grsec if possible. We really don't need all the options that grsec provides because our OS will not support users. We do have a real serious concern about breaking the functionality of our software. We just need buffer overflow protection (not reliant on the NX bit, i.e. most work on x86 CPUs in general, not just AMD64) and possibly systrace policies. The lowest impact on the OS is desired because we don't want to vastly complicate our build process.
Any input is still appreciated, but apparently there isn't a whole lot of real-world experience deploying these various patches on production (rather than personal) machines.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.