[BUG] User methods interfere with credentials passed in very-insecure-mode

[lashomb]

Describe the bug
When I try to run this when no user is logged in, ie: /Library/Management/erase-install/erase-install.sh --erase --silent --very-insecure-mode --credentials ${credentials}, I will get complaints like:

[get_user_details] Current user was not determined.
[user_is_invalid] ERROR - user was not validated.

I've also seen it pickup the user for a logged in user too, which wasn't the Volume Owner... I just want it to use the creds that are passed to it.

Before trying this project, I would just use the --stdinpass option for startosinstall, redirecting input into the process via <<<. That process does still work and can run at the login screen without a user logged in.

To Reproduce

• Issue a command to a Mac with no user logged in using the very-insecure-mode flag, ie: /Library/Management/erase-install/erase-install.sh --erase --silent --very-insecure-mode --credentials ${credentials}

Expected behavior
The script would pass through to startosinstall and finish the process.

Code/log output
The two functions I see that are problematic here in the output are following. Maybe these can be bypassed when using the very-insecure-mode flag.

[get_user_details] Current user was not determined.
[user_is_invalid] ERROR - user was not validated.

Environment (please complete the following information):

• OS version [15.3.2]
• erase-install version [37.0]

[lashomb]

In some initial attempts to modify the script and bypass the user methods, I'm able to get it to the startosinstall stage, and whats interesting is that the user passed in isn't coming from whats supplied using the very-insecure-mode option. Instead in my test, it ended up passing in --user ''.

I guess thats probably the crux of it, as what it's detecting as the active user might not be the volume owner or whats passed in for creds.