

…you assumed correctly, runit first released 2004, meanwhile systemd released 2010
…you assumed correctly, runit first released 2004, meanwhile systemd released 2010
The good within the bad
So, we’re right on track?
This one has reached the last stage, there’s nothing that can be done.
The affliction is terminal.
No that comes afterwards
What do i do before I did that?
in the Gmail app on Android and iOS devices
At least it isn’t my turn yet
Works for me with Voyager on mobile.
Intel Outside
You can nixos-rebuild
her, you have the technology.
All devices launching with Android 10 and higher are required to use file-based encryption.
To use the AOSP implementation of FBE securely, a device needs to meet the following dependencies:
- Kernel Support for Ext4 encryption or F2FS encryption.
Keymaster Support with HAL version 1.0 or higher. There is no support for Keymaster 0.3 as that does not provide the necessary capabilities or assure sufficient protection for encryption keys.
Keymaster/Keystore and Gatekeeper must be implemented in a Trusted Execution Environment (TEE) to provide protection for the DE keys so that an unauthorized OS (custom OS flashed onto the device) cannot simply request the DE keys.
- Hardware Root of Trust and Verified Boot bound to the Keymaster initialization is required to ensure that DE keys are not accessible by an unauthorized operating system.
https://source.android.com/docs/security/features/encryption/file-based?hl=en
Lose access to your MS account = lose your data forever. No warnings, no second chances. Many people learn about BitLocker the first time it locks them out.
It seems like they just got locked out of their Microsoft account (which stores the bitlocker key). Idk why they can’t just reset their password or if this article talks about the times where people couldn’t do that due to missing email access or maybe resetting the password deletes the bitlocker keys?
Either way though, the problem is that Microsoft is forcing encryption on everyone and not properly educating them on the consequences like “Backup your decryption key if you care about the data” in a way a normal user actually listens to.
But my streak is at 419, I can’t stop now!
Sounds like a problem fixing itself, at some point MacOS is going to have problems if it can’t edit a config is my guess.
Most backdoors are dangerous and dumb.
Why do you need EV certs?
Absolutely bamboozled
Actually, if you run anything and logout, it will be killed after a timeout. The way to prevent this in systemd land is to enable-linger for that user.
IMO this is a pretty sane default and it’s easy enough to disable for users
EDIT: For non-root users