In this lesson, we're going to talk about authorized restarts now before we go ahead and do that,
let's take a look at our file status and so we can see that five is on, we're fully encrypted.
And now it's showing here that both administrator and Moha, they are both firewall users.
All right, so on this computer, I'm logged in as Moha of our network user, and so if I'm doing some
remote support with him and I'm going to need to reboot the computer, he's on the other end.
He's going to be able to decrypt the computer at boot.
Now, if I'm doing remote support on the computer, but a user's not around and the computer reboots,
then it's going to get stuck on the boot up screen and it won't be back up to the operating system until
somebody types in a file vault password.
So that's what we're going to try to get around and that's what the authorized reboot is for.
So let's go ahead and take a look at the code.
And you can see that we're going to be downloading that same file.
Police file is we did when we installed firewall.
So that firewall pellis file, as you remember, just got the username and password and clear text of
a file vault user.
And in my situation, I still have it being the administrator username and password.
So once again, we're going to download it to the temp folder and then we're going to be running the
file of all command line with an off restart parameter.
And we're going to take input.
From our list file, so it's going to know the username and password that's going to be allowed to authorize
the restart, and then when it's done, it's going to remove that plus.
So let's go ahead and do an authorized reboot, and it's going to know our username and password because
it's in the post file.
And again, I think it's worth saying store the police file not on a public Web server, but a private
location.
And you can see now that the computer is performing a restart.
And we'll see that normally at this point on a file vault enabled machine, we would have been prompted
for a username and password to decrypt the hard drive.
But we're booting straight up into the operating system.
And in a moment, we'll end up at a rate or a login screen.
All right, so as you can see, we're back at the login screen and we should be able to log back into
that computer.
And so here we are logged into that computer and we can continue our remote support.
So if you have file vault encrypted machines and there's no one at the other end, you can perform this
process and still be able to reboot the machine and continue support on it, even though there's no
user to enter the firewall password.