Timeline for Change OSX encryption filevault password to match login pass
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2019 at 20:12 | comment | added | Devon_C_Miller | @Dmitri Yes, you should always have one properly synchronized user id. Even if it means creating a new user just to fulfill that role. Any time you work with any form of access controls, you make sure you have a way back in. Thankfully, I've not had an issue since that upgrade to Yosemite. | |
| Aug 19, 2019 at 11:52 | comment | added | User366 | You can check existing filevalut users with "sudo fdesetup list --extended". | |
| Aug 19, 2019 at 11:49 | comment | added | User366 | This is a bad thing to do if your user is the only one. You will end up in a filevault drive without a user to unlock. If you end up in such situation, the way to solve is to unlock the drive from the recovery mode using filevault recovery key in disk utility, then run terminal and run resetFileVaultpassword utility. This way you will get your user inserted back. But many thing will reset to default in macOS. Note that resetFileVaultpassword also works without unlocking the drive first but then it will not insert the user. So be extra careful with removing user with fdesetup. | |
| Feb 13, 2019 at 15:52 | comment | added | doekman |
I did this, but now AUserName is not listed anymore on the pre-boot login screen. I logged in as the other user, and fiddled a bit with the settings of the User & Groups preference pane, and now my AUserName appearas again in the screen.
|
|
| S Mar 14, 2015 at 20:43 | history | edited | klanomath | CC BY-SA 3.0 |
Fix typo 'fesetup' -> 'fdesetup' improved formatting
|
| S Mar 14, 2015 at 20:43 | history | suggested | kevin | CC BY-SA 3.0 |
Fix typo 'fesetup' -> 'fdesetup'
|
| Mar 14, 2015 at 20:35 | review | Suggested edits | |||
| S Mar 14, 2015 at 20:43 | |||||
| Jan 7, 2015 at 3:16 | history | answered | Devon_C_Miller | CC BY-SA 3.0 |