this post was submitted on 06 Jun 2025
120 points (96.9% liked)
Asklemmy
48731 readers
518 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
S3 sleep powers down all major components except for RAM. Modern sleep also keeps the CPU and network up, albeit in a low power state. It's not always executed well, hence the reports of laptops cooking themselves in a bag or draining overnight despite being "in sleep mode".
Also doesn't hibernate write your RAM contents to your disk? That sounds like a great way to leak your passwords and encryption keys in plaintext. Also you need to always reserve the same amount of space on disk as your RAM and can't use that space for anything else on the off chance you might want to hibernate.
At least for windows the hibernation file is stored as a file on the C: drive, so will be encrypted by bitlocker along with your other data.
Wouldn't that also mean that when the file gets overwritten, i.e the next time the system hibernates, you can potentially run a data recovery program on the C filesystem to leak its previous contents since modern filesystems don't necessarily immediately overwrite the underlying data anymore, but usually just change the regions on the drive the file points to? So you could have ghost memory dumps hiding out in your free space just waiting for malware to access. You can definitely recover data from the free space of a Bitlocker volume because the encryption is transparent to the filesystem.
This is also why I don't like swap files and always disable them (or use an OS like Fedora that doesn't have them by default), because it kind of defeats the point of only storing some data in RAM for security.
I could just be ignorant of how memory files in storage are managed though.
Ah, that's exactly what mine does sometimes.