3 ms·
The danger zobzu referred to was that the pages containing sensitive information might be paged out to disk. If that should happen, you're pretty much out of l
by amalcon 14y ago
The danger zobzu referred to was that the pages containing sensitive information might be paged out to disk. If that should happen, you're pretty much out of luck: they're just as vulnerable as anything else on disk.
The only defense against this is to make sure that the sensitive information is never paged out, using either mlock() or just not having any swap on your system.
There's also the class of bug whereby the software starts spitting out stuff from somewhere in memory that was never meant to be displayed, a la the Minus World in Super Mario Bros. Those are much less common in these days of memory protection and high-level languages, but it is still a concern.
- CrLf 14y agoYou can have encrypted swap.
- amalcon 14y agoThat's correct, that is a viable third option.
- tomkinstinch 14y agoEven if you keep things exclusively in memory, the information is still vulnerable via cold boot attacks: https://citp.princeton.edu/research/memory/ https://citp.princeton.edu/research/memory/