![]() Other Mac models were addressed with macOS High Sierra 10.13.5. Impact: A malicious application may be able to gain root privilegesĭescription: A type confusion issue was addressed with improved memory handling.ĬVE-2018-4285: Mohamed Ghannam for: MacBook Pro (15-inch, 2018) and MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports) Impact: An application may be able to execute arbitrary code with kernel privilegesĭescription: A memory corruption issue was addressed with improved memory handling.ĬVE-2018-4268: Mac working with Trend Micro's Zero Day Initiative Impact: A malicious application may be able to determine kernel memory layoutĭescription: An information disclosure issue was addressed by removing the vulnerable code.ĬVE-2018-4289: shrek_wzw of Qihoo 360 Nirvan Team Especially if you care about security and privacy of your data.Impact: A malicious application may be able to access local users AppleIDsĭescription: A privacy issue in the handling of Open Directory records was addressed with improved indexing.ĬVE-2018-4470: Jacob Greenfield of Commonwealth School Believe me or not, but it is not something you should rely on. If Hibernation does not work for you… well, RIP. If you have to use HibernationFixup, you may want to update it to 1.2.1, currently only available from source. If you can boot with AppleRTC/FixRTC patches OFF without BIOS settings reset, disable them, they break stuff in macOS OsxAptioFix1/2/3 will NOT work with hibernation on 10.13.6 and newer, and they may be removed from the default Clover installer in the future (time to upgrade). Config changes (and driver updates) will benefit all the systems (starting from Yosemite if I remember correctly), not just 10.13.6 Revision 4515 incorporates them in Clover.Ģ) AptioMemoryFix must be R20 (b83c025) or newerģ) Boot → RtcHibernateAware must be set to YES Starting with 10.13.6 a lot of legacy code got (finally) ditched on Apple side, and some changes are necessary to get hibernation to work on hacks. Revision 4450 introduced a new key (Boot → RtcHibernateAware) which improved the situation with hibernation compatibility and reduced the impact of some security issues in this process. However, if RtcHibernateAware does not work for you, enabling AppleRTC patch and using HibernationFixup may be a safer workaround. You should DISABLE them if you have no issues with BIOS preferences afterwards or use HibernationFixup. Note, that AppleRTC or FixRTC patches effectively break hibernation by reducing the available RTC memory and avoiding encryption key preservation. While it is extremely recommended to be turned on if you rely on hibernation, it may not work on your hardware (should be fine on Ivy Bridge and newer at least), and is thus optional and disabled by default. This option relies on a poorly documented (or rather undocumented) RTC memory access, and unspecified RTC memory layout, which is implementation-specific. To workaround this issue a new option enabling RTC memory erase upon waking from hibernation was added:īoot > RtcHibernateAware = YES (BOOLEAN, off by default) More details could be found in this message. To be used for Hibernation modes 25 & 3 with Lilu.kext and HibernationFixup.kext.Ī data leak issue was identified in the hibernation code, allowing hibernation encryption key to be passed to the system through RTC and preserved till the next hibernation without a subsequent erase. However, the graphics output protocol is not in anyway modified so if the OS draws after it is started then it is after the boot screen is drawn and will overwrite the custom logo, at least for now. The CustomLogo key can also be used under GUI/Custom/Entries in conjunction with BootBgColor for a different screen for every OS. If no option is specified then the boot screen will be drawn only for >= 10.10 Yosemite, so it remains compatible with previous behavior. - A base64 encoded PNG, BMP, or ICNS data.Path - A file path to load a custom image from. ![]() None - Use no logo only background color, gray if not specified by custom entry.Theme - Use the theme boot screen for entry type - NOT IMPLEMENTED.Alternate - Use the alternate white on black apple logo.Apple - Use the default gray on gray apple logo.true - Uses the default boot style, Apple.CustomLogo OR OR Apple/Alternate/Theme/None/Path OR PNG/BMP/ICNS base64 data Įnable the drawing of the custom boot logo. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |