A less hackish, more portable approach would be to make a new thread to handle the sensitive data and map/unmap the memory for its stack yourself if supported.
If you can't trust that user processes can't read physical memory they don't own, your OS is just crap. You can't mitigate this at user app level.
-
-
OTOH I'm showing a way you can mitigate inability to express in thd HLL (at least C) that certain data & everything derived from it is sensitive and must not be kept around.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.