this post was submitted on 15 Apr 2025
133 points (97.8% liked)
Technology
68918 readers
4742 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why is a reboot necessary for that? Is it not possible to enter the same encrypted state the phone is in after a reboot without actually rebooting?
Much of the data on your phone, including critical information that's required to run the operating system and make the device function, is fully encrypted when the device is off/rebooted.
While in this locked down state, nothing can run. You don't receive notifications, applications can't run in the background, even just accessing the device yourself is slow as you have to wait for the whole system to decrypt and start up.
When you unlock the device for the first time; much of that data is decrypted so that it can be used, and the keys required to unlock the rest of the data get stored in memory where they can be quickly accessed and used. This also makes the device more vulnerable to attacks.
There's always a trade off between convenience and security. The more secure a system, the less convenient it is to use.
I'm generally aware of all that, but I don't see how it answers the question. Why can't you just stop all app processes, unmount the relevant partitions, clear any memory containing cryptographic keys etc. but not actually reboot?
Rebooting just seems like a very roundabout, slow and inefficient way to get back to that initial state you describe. Is there something e.g. the bootloader does that cannot be replicated on a running phone and is essential for securing it again after the first unlock?
It's exactly what the reboot process is designed to do; return you to that fully encrypted pre-boot state. There would be no purpose to implementing a second method that does the exact same thing.