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: Fedora, little of centos, opensuse,ubuntu
Posts: 2
Rep:
pax aslr problem
Hi,
Is it that pax aslr is disabled in kernel 2.6.31 or gcc 4.4.2? I have tried on both Fedora 12 and Ubuntu 9.10. I wrote a small C program and used gdb to see the addresses on the registers esp ebp etc.. and they seem to be the same every time I recompile and rerun the program using gdb. I had tried this long ago on Fedora 10 and it work correctly at that time and the addresses in those were getting randomized. I made sure that kernel.randomize_va_space is set to 2 instead of to 0 . I am not very knowledgeable on this, so I might also be doing a silly mistake. If anyone has an idea why this is happening it would be great to let me know
Thanks,
Vikram Gade
I heard that Ubuntu made some improvements in security has they now use as default the "hardening option" during the compilation:
- stack protector
- ASLR
What do you think of it ?
I also heard some criticize saying that they do it, to tell it to the world, but the implementation is poor.
Any opinions ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.