- whoever
free()
-ed RAM w/o 0-ing passwords is the guilty party - padding 4 bytes here and 3 bytes there - hopefully not that much space to leak info..
On a more serious note wouldn't it be nice to have both options?
Alternative to my earlier idea on rustFreeze
:
- write
rustFreeze
inasm
- make it aware of page size somehow
- for each page in range read first 8 bytes and write them back
This should tame even MADV_FREE
right?