even just accessing the device yourself is slow as you have to wait for the whole system to decrypt and start up.
that’s not true. the system does not decrypt itself in one go. it’ll just wait with part of the bottup process until you unlock your device, and then keeps the encryption keys in memory so that it can encrypt and decrypt anything when needed.
and the purpose of the reboot is just to make sure that both the encryption key, and any data crumbs left in the memory get lost from there
While in this locked down state, nothing can run.
that’s not true either. for instance the system definetly runs with a couple of its components. but apps too can request to be able to work before unlock, like your alarm clock. but of course, apps that store data in the compartment accessible before unlock is not secure, however they can selectively store there only the most essential things needed to work (alarm time database and maybe used ringtones)
lol@discuss.tchncs.de 3 days ago
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 partition(s), 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.
Darkassassin07@lemmy.ca 3 days ago
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.
WhyJiffie@sh.itjust.works 2 days ago
its done that way because at a reboot all memory is lost, and it can’t happen that something slips through because there is a bug or some miscalculation