Boot Process with active EFI Firmware Password

I have a MacMini with Linux installed (for an embedded application) on the internal hard drive, and Mac OS X 10.5.6 available on an external Firewire / USB drive. The machine is a 1.83 MHz 2008 production unit with EFI version MM21.009A.B00 firmware installed (no later update is reported as available via the OS X Software Updater).
The system normally boots from the internal (Linux) disk without user interaction when first powered up.
In order to restrict users from starting the system from alternate devices, we activated an EFI firmware password. After doing so with the Open Firmware Password application on the OS X installer DVD (booted with option key and selecting the DVD icon, or with the C-key held), the system no longer automatically boots either of the two available hard disk devices. Rather a flashing file folder icon with question mark appears when the machine is powered up without any user interaction.
With the EFI password active, it is necessary to hold the option key down, enter the password, and then select the desired disk device icon (either internal Linux or external OS X device) in order to boot the system. It appears that the system can no longer automatically select a boot device when started up, even if only one is available. This requires that every user of the embedded system must know the EFI password in order to start the system. This seriously compromises the protections that a user would expect to achieve by using the EFI password capability.
Is this the expected performance of the firmware after the EFI password has been activated, or is this performance the result of a design flaw in the EFI code when the firmware password is active (i.e. is this a"feature" or a bug)?

Welcome to Apple Discussions!
The EFI firmware protection is there for people who work in environments where their machines must be secure from intruders, and secures information in event the machine gets stolen. If that sort of protection is too much for your needs, just setup your security and account preferences to log out when energy saver and/or screen saver is activated, and automatic log on is disabled. That's pretty good unless a person who steals your machine or has access to your machine has the original discs which came with the Mac, or newer retail operating system (up to the limits of the machine's hardware). So consider how much security you need, and you can ask the system to be that secure.

Similar Messages

How can I remove an EFI firmware password in a 2012 MacBook Pro Retina?

This computer was bought used. The SSD in it is dead, and it has an EFI firmware password blocking all my boot options. How can I remove it? The closest store is 400 miles away.

"YOU" CAN'T. You need to take the system to an Apple store or possibly an Apple Authorized repair center and ask them to remove it.
If you bought it used contact the original owner and ask for the password. Once you know that "YOU" can remove it.
If you come back with I can't get in touch with the original owner then I have no more help for you. Take it to your nearest Apple store.

EFi/Firmware Password and Recovery Partition

Before I get my Macbook Air, I want to know, does having an efi password set prevent you from booting with cmd+r without the password.
I already know that Cmd+s, Cmd+opt, cmd+opt+p+r, do not work.
It would be great if someone would just test it on their Macbook Air running Osx Lion with a firmware password set, and tell me if the Unlock dialog comes up.
Thanks!

I'm pretty tired but when I had Firmware pw set, it boots instantly into your login dialogue and then proceeds to load (or not load) the OS. So unless I'm being re.tarded, as soon as you enter in the firmware password, you're effectively starting from where you'd be if you didn't have the password set.
To your question, I'm 95% sure that yes, you would be prevented from getting around the firmware password. I don't think you could...? I'd test it for you but my recovery partition has melted into the lba - apparently....

Removing EFI Firmware Password

When I bought my MacBook Air in February 2011, it came with OSX 10.6.6. Since then I have set the firmware password, and then upgraded to 10.7 and now 10.8. Currently at 10.8.2.
I now have to do something that requires me to boot in safe mode. To be able to safe boot I have to unset the firmware password (fortunately, I know the password).
But how do I go about removing the firmware password? Do I use the USB key with 10.6.6 software on it? Or do I use software from the Recovery partition on the HD?
Do I have other options?
Thanks for your comments.

You can use the one you want, but as you are running Mountain Lion, you can use Recovery HD.
1. Press Command and R keys while your Mac is starting to start into OS X Recovery.
2. When it has started, go to Utilities menu and select the option to set up the firmware password.
3. Turn it off and restart your computer

EFI Firmware password question

Is there a commandline for the setting the EFI password using the Open Firmware Password Application ?
Thanks

Here's what I found:
Enabling Open Firmware Password
The Open Firmware password is a security feature available on modern Macintosh systems. If you enable the Open Firmware password, the computer will execute a secure boot sequence. Specifically, enabling the Open Firmware password prevents users from starting up the computer from a volume other than the chosen as the startup disk (chosen in the Startup Disk preference panel within the System Preferences.) Also, enabling the Open Firmware Password prevents users from booting into single user mode using Command-S key combination at boot time.
There is currently no public programmatic solution to setting the Open Firmware password (r. 3075615). This means this setting can not be set by an installer. However, an administrator can enable the Open Firmware password using the "Open Firmware Password" application located at: http://www.apple.com/downloads/macosx/apple/openfirmwarepassword.html
This was taken from Technical Note TN2062.
Sorry, but best I can do. Maybe you'll have better luck if you post the question in the Unix Forum.

Any issue and/or advice with activation of global password policy (10.9 osx server) ?

Hi Pro,
I have an OD domain (10.9.1 server) with 20 users mobile account (10.9.1 osx) authentification, I’d like to enable a global password policy, and I'm curious what actually happens when I add some policy in Server Admin > Open Directory > gear > edit global password policy?
If I set a "reset every 45 days" option, is that from the time the policy is enabled, or from the time the user account was created?
Any issue with Keychain ?
If I set a "must have one letter" or "numeric character", etc...and the user doesn't currently have a password that matches this criteria, will they be forced to set a new password immediately, or the next time one is initiated, did the account will be disable?
I just trying to prevent any bad experience for the users.
Thanks

Hi,
The 45 days will start from the moment you enable that setting for all active users, and will start whenever you create a new OD user.
There won't be any issues with Keychain, it will updated when a new password is set. On that specific day when they login or restart, they need to choose a new password. Keychain will update automatically.
The new policy will start working after the 45 days have been set. After 45 days that policy will be enforced, not before, users can continue to work with a less secure password. About 10 days before that deadline or earlier they will get an option in their login screen to renew their password because it will inform them it will expire soon.
You might want to notify all users of a new password policy when you set it and then inform them again about a week before it will expire. That will ensure a smooth transition...
Goodluck!
Jeffrey

Boot process with votes messages:[vxclust]: [ID local0.error] master_vote:1

Hi Gurus.
I have two node cluster (node1 and node2) when we boot the cluster check the message (boot process):
Jan 23 14:47:23 node2 ID [vxclust]: [ID 821894 local0.error] Selecting master ...
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696243 local0.error] count:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 246593 local0.error] mvotes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 843298 local0.error] votes[mvotes[count]]:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 938531 local0.error] master_vote:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696243 local0.error] count:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941912 local0.error] votes[count]:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759296 local0.error] value:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696244 local0.error] count:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696245 local0.error] count:2
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696246 local0.error] count:3
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696247 local0.error] count:4
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696248 local0.error] count:5
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696249 local0.error] count:6
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696250 local0.error] count:7
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696251 local0.error] count:8
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 696252 local0.error] count:9
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641765 local0.error] count:10
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641766 local0.error] count:11
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641767 local0.error] count:12
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641768 local0.error] count:13
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641769 local0.error] count:14
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641770 local0.error] count:15
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641771 local0.error] count:16
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641772 local0.error] count:17
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641773 local0.error] count:18
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 641774 local0.error] count:19
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762324 local0.error] count:20
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762325 local0.error] count:21
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762326 local0.error] count:22
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762327 local0.error] count:23
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762328 local0.error] count:24
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762329 local0.error] count:25
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762330 local0.error] count:26
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762331 local0.error] count:27
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762332 local0.error] count:28
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 762333 local0.error] count:29
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID [vxclust]: [ID 624920 local0.error] count:30
Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID[vxclust]: [ID 624921 local0.error] count:31
Jan 23 14:47:23 node2 ID[vxclust]: [ID 941911 local0.error] votes[count]:0
Jan 23 14:47:23 node2 ID[vxclust]: [ID 759297 local0.error] value:1
Jan 23 14:47:23 node2 ID[vxclust]: [ID 385272 local0.error] Selected master:0
Jan 23 14:47:23 node2 ID[vxclust]: [ID 874465 local0.error] New assignment :0 node2
Jan 23 14:47:23 node2 ID[vxclust]: [ID 151115 local0.error] New assignment :1 node1
===================
If this is a problem how can we solve?
Many Thanks
Regards

You did not give a lot of information in order to know which Sun Cluster version you are using and if you are using Oracle RAC together with CVM.
To me it looks you have enabled CVM (VxVM with the cluster feature enabled) in order to use a shared diskgroup.
This is only allowd in combination with Oracle RAC. If this is what you are trying to use, have a look at http://docs.sun.com/app/docs/doc/819-2981/6n58037s2?a=view.
So those messages are CVM specific, and I guess they show the selection process of which node is going to be the master node for the shared diskgroup - in your case node2.
Greets
Thorsten

[SOLVED] DELL Vostro doesnt finish boot process with HDMI pluged in

I am using Xorg 1.16.1, when I try to boot my machine with a external monitor (HDMI) plugged in, X does not start.
Here is what dmesg says:
[ 7.368666] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504
[ 7.390077] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 157/256 dur 1762/1504
[ 7.528043] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
[ 11.048888] [drm:ibx_irq_handler] *ERROR* PCH transcoder A FIFO underrun
[ 27.815808] [drm:ibx_irq_handler] *ERROR* PCH transcoder A FIFO underrun
when I pull the HDMI cable out, X starts properly:
[ 53.849688] fuse init (API version 7.23)
This is what lspci says:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
Has anybody an idea, what could be wrong with my system?
regards
Last edited by ifelseforeach (2014-10-06 16:35:40)

Yea I m using light-dm.
Ok, I just did another reboot to check the log files in the plugged-in/out case and I discoverd, that the boot process can not be completed as long as the HDMI cable is plugged in. (So my first Headline was unintentional right : ) )
I checked dmesg I both cases and they only differ only in the last few lines:
PluggedIN case dmesg:
[ 7.411395] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504
[ 7.429694] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 157/256 dur 1762/1504
[ 7.520580] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
[ 60.760060] [drm:ibx_irq_handler] *ERROR* PCH transcoder A FIFO underrun
[ 67.101403] fuse init (API version 7.23)
As you can see at the time stamps, the boot process stops as line 3 and only continues at line 4 when I pull out the cable.
PluggedOUT case dmesg:
[ 7.325765] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504
[ 7.347581] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 157/256 dur 1762/1504
[ 7.515908] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
[ 14.652575] fuse init (API version 7.23)
Last edited by ifelseforeach (2014-10-04 21:26:20)

How efi firmware password macbook pro luck I forget password and I want rest this password

I updated my MacBook Pro to the last update two days ago and when you activate served Aye Claude lock the device and the back of my four secret numbers I do not know. When you do Recovery Mode BIOS lock what is the solution

The best thing to do is to take the MBP to the Apple store and let the Genius do it for you.
Best.

Ibook g4 firmware password

i havent used my ibook in many years . as since the computer has been put up for a while.. was going to give as gift to grand adughter but i have a firmware password on it and have forgotten it .. as its been years since it has been used.. have the original disc but cannot even boot up with it as firmware password needed. is thaere a way to bypass password . and reload osx ? help

Nope. That's the point of the Open Firmware Password. To prevent anyone from access. If you go to an Apple service center they should be able to help you.

Booting into Single User when having Firmware password protected...?

Hi,
I have to put a number of iMacs to the laboratory so that users could log on but without administrative rights. In order to prevent them from booting the external devices and booting into single-user to gain root access, I have set the Firmware password, which does a nice job of blocking "C" and "CMD-S", etc commands during the bootup.
However, I wonder: in some occasions when we need to perform some troubleshooting, we could not boot the system into single-user mode. I know that I could press "Option" key during the startup, which will bring into the "Startup Manager". After then, the Manager shows the devices for booting. I find that even when I double-click the "Macintosh HD" and then press "CMD-S" immediately, the system does not perform single-user booting. Of course, pressing "CMD-S" when the Mac starts up does not work as well, as this command is blocked due to the Firmware password set.
I wonder if there is a way for us, the system administrators, to get into the single-user mode in this case. Of course, I do not expect an answer of getting an Installation DVD, booting the DVD, involving the Firmware Password Utility to disable the Firmware Password, in order to gain back the single-user booting ability...
Thanks.
Dominic

For Mac OS X, setting an firmware password will lock out all commands. While Single user mode is useful for troubleshooting, it can also be used wrong by the wrong people which is why it is disabled along with the rest of the 'startup commands'
So a few thoughts here:
- I'm asking in this case: does holding down the option show network drives in server situations such as yours? If so, you could have a network server (network startup disk) to start the computer from to do the trouble shooting you need and still be able to keep the firmware password in place
- I've been reading up on Unix commands lately and found a nice gem: nvram. Being a unix admin, you may already be familiar with it. It's the unix command for working with open firmware variables.
When you use the firmware utility to set the password the 'security-mode' variable is set to 'command' by default. I know there are two other options: 'none' (no password set) and 'full' (don't know what else this blocks). Is it possible that there is some way to selectively block the commands you want to stop (startup from other drive, zap pram, etc) but still allow Single User Mode?
Not sure myself, just putting something out there. Maybe it'll spark something for ya.

Intel iMac, Open Firmware Password Protection and booting from CD

I have an Intel iMac I'm setting up for use in a public library. I want to prevent single user login with the Open Firmware Password Protection utility, but if I do, how do I boot from the OS disc, zap PRAM, etc? The OFPP page has instructions on removing the OF password, but it does not work on Intel Mac's. Also, is there an alternative way to prevent single user login?

No, you were right, I just misunderstood. Technically it's called single-user mode. But, you were right.
Anyway,
Since it seems that there might not be an answer directly related to your topic you could maybe give this a try.
In Simple Finder the user can not restart or shutdown. They can only sleep and log out.
The other problem, however, is if they log out then there are those Sleep, Restart, and Shut Down buttons on the login screen. Luckily, though they can be turned off.
So as of now, if some is logged in in a Simple Finder account they can not restart or shut down the computer in order to get into single-user mode. They can also not get into the Administer account since it is password protected.
The only problem I can see with this is that a person could do a hard shut down, hold the power button down until it turns off, and then boot up and enter single-user mode.
If you want to go ahead and do this, in order to get the computer up and running in the mean time, just post back and I'll be glad to help you set up a Simple Finder account.

What's the ActivityMonitorD process? -- Activity Monitor with a 'D'

So I've been monitoring my computer's processes with Activity Monitor, working through some possible bugs with a hard drive and I found that there is a process running that isn't listed here: http://triviaware.com/macprocess/all
Anyone know if there is a process called: ActivityMonitorD
That's right *'ActivityMonitor' with a D on the end*. That is a process in addition to the regular 'ActivityMonitor.app'. Anyone able to solve that riddle for me?

What do I make of this information in my Activity Monitor:
PID    Process Name                    User
1        launchd                              root
323       acticitymonitord                root
51          autofsd                           root
50          blued                              root
162        com.apple.dock.extra       root
14          configured                       root
107        coreaudiod                      root
53          coreservicesd                 root
95          CVMserver                     root
13          diskarbitrationd               root
54          diagnostic                      root
44          dynamic_pager               root
253        filecoordinationd              root
15          fsevensd                        root
52          hidd                               root
40          KernalEventAgent           root
10          kextd                             root

Protect macbook with Open Firmware password

Hi. I'd like to protect my MacBook air by enable an Open Firmware password.
How can I do it ?

Open Firmware was available in PowerPC-based Macs, so your MacBook Air hasn't got it. Instead, it's a EFI firmware password, that will ask you for a password every time you want to start in a mode different than the normal one (without holding any key while your Mac is starting up).
To enable it, hold Command and R keys while your Mac is starting to start up into OS X Recovery. Then, go to Utilities menu (on the menu bar) > Firmware Password Utility, and enable it.
Don't forget the password. Only Apple knows how to reset it, so you will have problems

Firmware password deactivate

Hello. Have a problem with disabling the firmware password and although I come with a pasword into recovery mode and using the firmware password tool, try with the same password to disable and it doesn't work. Error: password is wrong but it's definitely the same password as the login after the start with pressing the Alt key. Maybe that will help further: File Vault 2 was previously active and now off again. Thanks for your help.

Hi Aivengo,
I need to modify the firmware password of my late 2011 Mac book pro but I have the same issue as yours.
I can enter EFI boot interface entering my firmpasswd, but unable to modify or desactivate the password.
It says invalid password. It does not recognize my current EFI password.
I've never used filevault 2
Any Ideas?
thanks

Boot Process with active EFI Firmware Password

Similar Messages

Maybe you are looking for