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.
I need to ensure that objects stored in memory are no longer accessible, even when that memory is freed up for other uses. How does Linux handle this? Is there an overwrite operation performed for released memory?
The OS is responsible for reallocating freed memory for reuse. It generally doesn't care what that memory contains or what it was used for. Freed memory is dumped back into the pool and allocated on first come first served basis so trying to grab particular memory data would take a concerted effort. That said, memory cleanup, especially for securing stored information, is primarily the responsibility of the application, not the operating system.
Thank You....Should Have Known It's An Application Problem
Hitting myself upside the head ....I should have known better....thanks. This makes sense. An application could probably do this when the object is destroyed as part of the teardown method.
Grsecurity has an option to "Sanitize free memory" which will overwrite the memory a few times (3?) when it is freed up. There is a small performance hit in general but with all the security options of grsecurity the performance hit overall is normally 2-3%.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.