>And don't start me on the sound signals like the stove complaining it got a drop of water on its sensitive touch buttons placed right next to the pot.
I believe this is actually a safety feature: When a pot boils over and spreads water on the touch panel, both the pot and the touch panel may be too hot to touch, leaving no way to turn off the stove. So, to be on the safe side, the stove turns off and beeps.
> we do hour offsets twice a year, so if an hour off is okay why is 1 second off not?
The actual Unix time does not change when the clocks are switched between daylight saving time and standard time. Only the time zone changes.
When a leap second occurs, the actual Unix time changes, which can lead to bugs, e.g. when a positive time difference comes back as negative. To prevent such issues, a monotonic clock can be used to measure time intervals.
Edit: OK, just re-read some docs, looks like POSIX chose the worst of all options and decrements the timestamp experiencing the same second twice...
Wrong info from before edit: Unix time doesn't change either, it's the number of seconds since 00:00:00 UTC on 1 January 1970, though systems may or may not ignore that and set it to match the UTC time.
Yes. It does. Op is correct. A leap second specifically is an adjustment because “how many seconds since 1970” changes because the earth’s rotation isn’t constant speed. UTC tone definitely changes. If it didn’t then you wouldn’t hear anything about it and it would just be transparently folded into your time zone database.
There would still be a temperature difference for some time after entering a PIN until the keys used are fully cooled. So this method might not fully mitigate the attack.
A better solution could be to heat the keys to about the same temperature as a human's finger tips, so that no heat is being transferred while entering a PIN.
Exactly, easier and much more effective than the mitigation suggested by the scientists:
>One potential risk-reduction pathway could be to make it illegal to sell thermal cameras without some kind of enhanced security included in their software.
Maybe something loosely similar to the protection that is said to be present in very high level colour photocopier that prevents from photocopying money?
I believe it's not about customer enjoyment, it's about profits. If a customer spends more time on the website, they might buy more stuff they don't even need.
It's the same reason why you have to waltz to the back of every supermarket to buy essential items, walk back to the front, and look at individually packaged, overpriced snacks for several minutes while waiting in line at the register.
I create a separate user for each app, and use the systemd exec configuration [1] for sandboxing [2]. Some apps only get read-only access to their own files, and no Internet access, for example (along with many other restrictions). I have some systemd drop-in units that I frequently reuse.
For standard services, I use Apparmor with the default `apparmor-profiles`, as well as fail2ban with some additional firewall rules.
Regardless, I'd also recommend setting up the hardware watchdog just in case. It's saved me in the past when I overloaded my Pi with a bad cron job.