←back to thread

286 points joegibbs | 10 comments | | HN request time: 0.83s | source | bottom
Show context
arcticbull ◴[] No.42143642[source]
Periodic reboots are actually a PCI requirement for payment terminals heh, basically every point of sale on the market reboots every 24h.
replies(5): >>42143696 #>>42143718 #>>42143892 #>>42144077 #>>42144547 #
Gigachad ◴[] No.42143696[source]
Seems like a good defence in depth strategy. These days most systems have a pretty good boot chain security, so after a reboot you know the system is in a valid state and any potential malicious changes have been flushed out.
replies(5): >>42144335 #>>42144436 #>>42144554 #>>42144910 #>>42147261 #
DaiPlusPlus ◴[] No.42144335[source]
Probably also helps with other kinds of transient hardware faults (and cosmic-rays) that can cause bitflips.

That said, on principle, there is no reason why ECC RAM should not be the standard (c.f. Linus Torvald’s ire at Intel using ECC as a market-segmentation ploy)

replies(1): >>42145042 #
1. close04 ◴[] No.42145042[source]
> reboots the phone if it’s not unlocked for 72 hours

Scheduled reboots would help more with clearing malware or transient errors.

But for now, for anyone periodically using the phone, which I bet is most users, the phone will never reboot automatically.

replies(2): >>42145110 #>>42145399 #
2. derefr ◴[] No.42145110[source]
Not never; phones also reboot when there are critical OS updates to apply — and that happens as long as the phone is both charging and locked at any time during a vendor-defined daily maintenance window (usually something like 2AM-4AM in the user's local time.)

This happens even if the user just put the phone to sleep a moment ago. The only way to prevent it is to never leave your phone locked and charging at the same time.

replies(1): >>42145150 #
3. close04 ◴[] No.42145150[source]
> phones also reboot when there are critical OS updates to apply

Of course, or when they run out of battery, or you drop them too hard, etc. But realistically you could go for weeks or months without a reboot. From a transient fault or malware perspective, that might as well be never.

replies(1): >>42145257 #
4. derefr ◴[] No.42145257{3}[source]
"Critical security updates" for iOS come ~weekly.
replies(1): >>42145450 #
5. TeMPOraL ◴[] No.42145399[source]
> But for now, for anyone periodically using the phone, which I bet is most users, the phone will never reboot automatically.

Samsung has an auto-reboot daily feature and has been pushing it a lot (in form of annoying notifications and settings suggestions). In principle, it may not even be a bad idea - but for one fact:

Rebooting the phone effectively turns it off. Until the user unlocks the phone, it won't connect to phone network. AFAIK it also won't start any of the usual background processes that listen to notifications, and it might not even connect to Wi-Fi.

Those "security" measures make automated reboots an useless feature. There really is only one good time to auto-reboot, and that's when the user is sleeping. But no way anyone's doing that when it means their phone won't be able to receive calls. Even during the day, the phone randomly rebooting and remaining disconnected until the user notices - it's probably even worse, and I imagine anyone would disable this feature after first time it activated.

replies(3): >>42145513 #>>42145599 #>>42145722 #
6. saagarjha ◴[] No.42145450{4}[source]
This is definitely not true. Apple releases security updates about once a month.
7. nyargh ◴[] No.42145513[source]
I'm not sure this is true.

I have a Samsung with this feature. It rebooted overnight and this morning it was in BFU state with several mail and sms notifications. It was also connected to wifi and the cellular network.

replies(1): >>42145533 #
8. TeMPOraL ◴[] No.42145533{3}[source]
It was true for my Galaxy S22, and is currently true with reboots after update. And yes, early on I had a situation where the phone rebooted overnight and remained stuck on the lock screen while disconnected from networks, until I woke up and noticed. Fortunately I didn't miss anything important, but after that I immediately reviewed all settings and disabled anything that could reboot the device automatically (including updates, which are set for manual installation now).
9. gambiting ◴[] No.42145599[source]
>>Rebooting the phone effectively turns it off. Until the user unlocks the phone, it won't connect to phone network. AFAIK it also won't start any of the usual background processes that listen to notifications,

Well yes, because the storage and all the apps are encrypted until you unlock your phone. So you could have all the apps boot up and start listening for events, but it would be at the cost of reduced security elsewhere. Not sure what the right solution is tbh, I think personally I'd rather have all of my data encrypted even if it means my phone isn't actually "active" after a reboot.

10. BrandoElFollito ◴[] No.42145722[source]
> Until the user unlocks the phone, it won't connect to phone network.

This is not true in my case (Samsung Galaxy S22+). The phone is fully operational after a reboot, connected to GSM, 5G and Wi-Fi