• 0 Posts
  • 33 Comments
Joined 2 years ago
cake
Cake day: June 4th, 2023

help-circle

  • The key enrollment that Mint did sounds like registering the Machine Owner Key (MOK). That basically tells the bios that anything signed with that key should be permitted. The MOK is especially required when compiling your own drivers. Anything shipped by a Linux distro should already be signed so that the shim will permit it. SecureBoot is more about making sure your boot files haven’t been tampered with rather than being about preventing the owner from doing something.

    You should already be able to boot any modern Linux OS that has support for SecureBoot. Only if you compile your own drivers or kernel would you need to use a MOK. If you do need that, you should be able to enroll another MOK or copy the MOK key files from the Mint install and use those keys to sign drivers in any other Linux distro.

    The cli program mokutil will let you view and export your enrolled MOKs.










  • Assuming that you trust what Proton says, when they receive a (possibly unencrypted) message they re-encrypt it with your key as soon as possible and they don’t log the content. So, after that point, they (or anyone else) can’t read the email contents. If it was also encrypted in transit, then there’s only a small window inside their email processing system where the plaintext was passed from one encryption to the other. It’s only decrypted again in your browser or proton mail app with the key that only you have. It’s not bulletproof, but it’s better than most providers.




  • Your domain name could be ordered to be removed from US-based dns providers, no matter which TLD it is. That would essentially block your website from most US-based viewers without actually shutting down your hosting. Advanced users could still get to it, though. Consider hosting through Tor and a .onion address for more resiliency.