{"id":2680,"date":"2017-11-30T12:04:12","date_gmt":"2017-11-30T17:04:12","guid":{"rendered":"http:\/\/z-issue.com\/wp\/?p=2680"},"modified":"2017-11-30T12:04:12","modified_gmt":"2017-11-30T17:04:12","slug":"rebooting-macos-into-recovery-mode-to-disable-system-integrity-protection-sip-without-the-command-key","status":"publish","type":"post","link":"https:\/\/z-issue.com\/wp\/rebooting-macos-into-recovery-mode-to-disable-system-integrity-protection-sip-without-the-command-key\/","title":{"rendered":"Rebooting MacOS into recovery mode to disable System Integrity Protection (SIP) without the command key"},"content":{"rendered":"

My love for Apple and especially MacOS does not run deep. Actually, it is essentially nonexistent. I was recently reminded of the myriad reasons why I don’t like MacOS, and one of them is that the OS should never stand in the way of what the operator wants to do. In this case, I found that even the root account<\/a> couldn’t write to certain directories that MacOS deemed special. That “feature” is known System Integrity Protection<\/a>. I’m not going to rant about how absurd it is to disallow the root account the ability to write, but instead I’d like to present the method of disabling System Integrity Protection.<\/p>\n

First of all, one needs to get into the Recovery Mode of MacOS. Typically, this wouldn’t be all that difficult when following the instructions provided by Apple<\/a>. Essentially, to get into Recovery Mode, one just has to hold Command+R when booting up the system. That’s all fine and dandy if it is a physical host and one has an Apple keyboard. However, my situation called for Recovery Mode from a virtual machine<\/a> and using a non-Apple keyboard (so no Command key). Yes, yes, I know that MacOS offers the ability to set different key combinations, but then those would still have to be trapped by VMWare Fusion<\/a> during boot. Instead, I figured that there had to be a way to do it from the MacOS terminal<\/a>.<\/p>\n

After digging through documentation and man pages<\/a> (I’ll spare you the trials and tribulations of trying to find answers \ud83d\ude1b ), I finally found that, yes, one CAN<\/strong> reboot MacOS into Recovery Mode without the command key. To do so, open up the Terminal and type the following commands:
\n
\nnvram \"recovery-boot-mode=unused\"
\nreboot recovery
\n<\/code><\/p>\n

The Apple host will reboot and the Recover Mode screen will be presented:<\/p>\n

\"MacOS<\/a>
\nClick to enlarge<\/em><\/center><\/p>\n

Now, in the main window, there are plenty of tasks that can be launched. However, I needed a terminal, and it might not be readily apparent, but to get it, you click on the “Utilities” menu in the top menu bar (see the screenshot above), and then select “Terminal”. Thereafter, it is fairly simple to disable System Integrity Protection via the following command:<\/p>\n

csrutil disable<\/code><\/p>\n

All that’s left is to reboot by going to the Apple Menu and clicking on “Restart”.<\/p>\n

Though the procedures of getting to the MacOS Recovery menu without using the Command key and disabling System Integrity Protection are not all that difficult, they were a pain to figure out. Furthermore, I’m not sure why SIP disallows root’s write permissions anyway. That seems absurd, especially in light of Apple’s most recent glaring security hole of allowing root access without a password<\/a>. \ud83d\ude33<\/p>\n

Cheers,
\nZach<\/p>\n","protected":false},"excerpt":{"rendered":"

My love for Apple and especially MacOS does not run deep. Actually, it is essentially nonexistent. I was recently reminded of the myriad reasons why I don’t like MacOS, and one of them is that the OS should never stand in the way of what the operator wants to do. In this case, I found … <\/p>\n

Continue reading<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[151,139,15,152,153,35,59],"class_list":["post-2680","post","type-post","status-publish","format-standard","hentry","category-technology","tag-apple","tag-code","tag-image","tag-mac","tag-macos","tag-security","tag-software","item-wrap"],"_links":{"self":[{"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/posts\/2680","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/comments?post=2680"}],"version-history":[{"count":9,"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/posts\/2680\/revisions"}],"predecessor-version":[{"id":2689,"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/posts\/2680\/revisions\/2689"}],"wp:attachment":[{"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/media?parent=2680"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/categories?post=2680"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/z-issue.com\/wp\/wp-json\/wp\/v2\/tags?post=2680"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}