The main purpose of this is actually security. Because when the device is in BFU (before first unlock) state, it's much harder to gain access to the data (without the correct unlock credentials). During the reboot, the encryption keys are wiped from RAM, making it essentially impossible to access the device, since brute-force unlock attempts are prohibited by Weaver API, which is enforced by the Titan M2 hardware security module. You can read more about this at https://grapheneos.org/faq#encryption
impure9435
joined 6 months ago
Use archive.is to access the full article
It's not maintained anymore. The last commit is 8 months old. Use Bypass Paywalls Clean instead, here's the Firefox version: https://github.com/bpc-clone/bypass-paywalls-firefox-clean
Kodi is ideal for an HTPC
We need a successful replacement to DirectX for this to happen.
Vulkan?
I don't really remember, that was a few years ago. I've been using the flatpak ever since.
For me it was actually the other way around, I had issues with the normal package so I went with the flatpak.
mail.tm is pretty nice for this. It's meant to be used as a throwaway email service, but you can also save the login credentials and reuse the email address if you need it more than one time.
It doesn't intentionally disable biometrics. Disabling biometrics is just a logical consequence of wiping the encryption keys from RAM. Your data is encrypted with your password as the key (not exactly, it first goes through a key derivation function, but the PIN/password is the entry point for the KDF). Your biometric information can't decrypt your data, as your data is not encrypted with your biometric information as the key. When using biometrics, the encryption key is kept in RAM, and the biometric data is only validated by the OS. No actual decryption occurs here. The data on your phone is only being decrypted during the first unlock after a reboot. That's why security states are grouped into BFU (before first unlock) and AFU (after first unlock).