On iOS there is the option to have the device delete all data after 10 failed login attempts. How can I have the same option on macOS so that my SSD gets deleted/reformated after x failed attemps to log into my user account?
With on-board tools (and without using external services like "Find my Mac" & "Erase my Mac remotely" via iCloud) it's impossible to erase or reformat the boot volume with
diskutil ... because the disk is busy.
You can remove your user folder though:
The method below uses a password policy and depending on the state of the user login capabilities, a launch daemon and a bash script invoked by the daemon will remove the user folder.
Create a password policy plist on your desktop:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>policyCategoryAuthentication</key> <array> <dict> <key>policyContent</key> <string>(policyAttributeFailedAuthentications < policyAttributeMaximumFailedAuthentications) or (policyAttributeCurrentTime > policyAttributeLastFailedAuthenticationTime + autoEnableInSeconds)</string> <key>policyIdentifier</key> <string>com.apple.maximumFailedLoginAttempts</string> <key>policyParameters</key> <dict> <key>autoEnableInSeconds</key> <integer>31536000</integer> <key>policyAttributeMaximumFailedAuthentications</key> <integer>10</integer> </dict> </dict> </array> </dict> </plist>
The user login capabilities will be disabled after 10 failed login attempts for 31536000 seconds (=one year).
Create a bash script rmuserdir.sh:
#!/bin/bash PWPOL=$(pwpolicy -u username authentication-allowed) if [[ $PWPOL == 'User <username> is not allowed to authenticate: Failed global policy "com.apple.maximumFailedLoginAttempts"' ]] then rm -fR /Users/username fi
in /usr/local/bin/ and make it executable. Replace the string username with your user's name but keep the angle brackets in the if statement!
Create a launch daemon org.userdirrm.plist in /Library/LaunchDaemons/ with the content:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>org.userdirrm</string> <key>ProgramArguments</key> <array> <string>/bin/bash</string> <string>/usr/local/bin/rmuserdir.sh</string> </array> <key>RunAtLoad</key> <true/> <key>StandardErrorPath</key> <string>/tmp/org.userdirrm.stderr</string> <key>StandardOutPath</key> <string>/tmp/org.userdirrm.stdout</string> <key>StartInterval</key> <integer>60</integer> </dict> </plist>
File owner and group has to be root:wheel and file permissions have to be 644. The daemon will run every 60 seconds. You can tweak this by changing the integer in the key StartInterval.
Import the password policy:
pwpolicy setaccountpolicies ~/Desktop/pwpolicy.plist
You have to enter your (authenticator=admin) password.
Launch the daemon:
sudo launchctl load /Library/LaunchDaemons/org.userdirrm.plist
You can test the set-up by creating a stub user, changing the username in the bash script temporarily and entering wrong passwords trying to login with this stub user. You can lower the number of failed login attempts to 3 in the password policy temporarily to shorten the test.
adding the (rm) -P option in the shell script:
Overwrite regular files before deleting them. Files are overwritten three times, first with the byte pattern 0xff, then 0x00, and then 0xff again, before they are deleted.
trying to remove the root folder instead of your user folder:
rm -fR /
rm -fRP /
SIP protected files won't be removed/overwritten! To remove/delete/overwrite them also, you have to disable SIP.
- try to get the binary srm from an older OS X install, add it to High Sierra and use it in the bash script instead of rm. The binary srm securely removes files or directories. Check
man srmfor further options (I haven't tested this).
In my opinion the method outlined above can be circumvented by booting to Single User Mode, launching the opendirectoryd with launchctl (after the obligatory file system check and mounting the boot volume to /) and removing all password policies with
Therefore formatting or erasing disks or folders to "gain security" isn't recommended. Instead encrypt your main volume with FileVault2 and use good passwords for all users.