How was this encrypted so far? I could be misunderstanding things, but this brings up the specter of a universal unlock/backdoor key of some sort. Does that mean that Filevault works with 2 keys? And with the OS easily able to change access via password. To me what this really means is the entire drive was ALWAYS encrypted and now I set a key to it. So if that's so, why not let me lock the entire drive anyway, because the argument on performance/consumption of encryption goes away if everything is essentially always encrypted anyway. NO WAY that it processed that much data that fast, so that means these things are always encrypted from the start. THEN turned on file vault and the entire thing was "encrypted" in less than a minute, and now the container shows as an APFS Encrypted container. Because I just installed Big Sur fresh on a non encrypted APFS drive. It's made more weird because I'm pretty positive Big Sur is ALWAYS ENCRYPTING ALL CONTAINERS, just it will have a public key for containers that do not have "encryption" set on. Would love any thoughts/speculations on if this is a bug or a feature, and if it's a feature, WHY!?
Big Sur will and does work fine, but why require the crazy work around? The current work around is to install Catalina on an APFS encrypted drive, and then do an upgrade on that drive.
This is bad when you dont want the drive to be unencrypted at any time. However, this means anyone can simply flip the FileVault switch and undo encryption on the drive. Yet, if you install on a non-encrypted drive, you may later then select FileVault and the entire container will get encrypted per this thread: "You may not install to this volume because it has a disk password" However, now if you first format a drive as APFS Encrypted and try to use the Big Sur (latest 11.1, and earlier 11.01) onto that drive you get the following error: First as HFS+ Encrypted, and the last several years as APFS Encrypted. For many years I have formatted my system/boot hard drive as an encrypted drive.
0 kommentar(er)
