Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mojave no longer allows a different password for filevault and the user password. #338

Closed
hduarte opened this issue May 25, 2019 · 3 comments

Comments

@hduarte
Copy link

hduarte commented May 25, 2019

In Mojave the user password is used to unlock the user account and the filevault disk.

In high sierra one could set up a password for filevault and not allow users the ability to unlock the disk.
This had the benefit of in case of a stolen laptop that is shutdown, even if the attacker had the user’s password it couldn’t decrypt the disk.

Has anyone found a solution in mojave to have different passwords for user and filevault ?

@hazcod
Copy link
Contributor

hazcod commented May 25, 2019

Perhaps creating a separate encrypted APFS volume?

@kilo6eight
Copy link

This is pretty essential. Look at MacOS password-on-forwarding attacks to research more. If your threat model includes adversary who may wish to detain you and obtain contents off your HDD in decrypted state then you need to take following measures.

Create 3 accounts:

1 - Admin (Only used to unlock filevault disk, account is never used other purposes)
2 - Admin #2 (Used to perform admin functions)
3 - User Account

Once you have created the three accounts you need to use sysadminctl to remove SecureTokens from account #2 and account #3.
Result is only account #1 can authenticate and unlock filevault account. Outside of the BA environment you never use your account #1 password.

Use a Mac with T2 chip.

@drduh
Copy link
Owner

drduh commented Feb 6, 2020

Please send a PR with updated instructions to the Admin and standard user accounts section.

@drduh drduh closed this as completed Feb 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants