No, if I wanted to get a lot of likes, I'd post some decent photos on the "shot of the day" monthly threads. It's incredible, everyone's so friendly and supportive! 🤣
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
@ DeeVeeDee Dear Sir, let it go, this is turning into an ego boost contest. I dare to say that most readers here appreciate the concern regarding security, but I for one do not need your apologies. Your perspective regarding security is valid in most regards, enough said, let it rest. Now we can get back to "Sonoma on our old Macs."
Personally, I think it is probably safe enough to use my old iMac with Sonoma and OCLP, compared with running no-longer updated Big Sur OS, especially as I will not be using it for banking in any form or even purchases on the net, or mail. The quality of the recent OCLP versions is self-evident. Kudos to the devs and thanks for the tremendous efforts!
All smooth sailing for this Dutch MacBook Pro 11,5
-Give it Some time to index en cool down and it's fast en responsive again.
-Widgets are light to.
-Give it Some time to index en cool down and it's fast en responsive again.
-Widgets are light to.
Let’s try to be positive: since OCLP currently requires breaking the seal and partially disabling SIP… how could this be mitigated…? As I’ve said many times, with Monterey you could run a root patched Metal Mac with SIP enabled and only SSV disabled (which worked fine with my MBP11,3); requirements for Ventura and Sonoma changed that, so it’s not possible anymore to fully enable SIP. Talking about the SSV, leaving it untouched would probably require all patched extensions to be on the Data volume (à la auxiliary collection): would this even be possible, at all…? Are there other ways to solve these problems? Who knows?
Last edited:
I get that this conversation became a little uncomfortable for those who are not confrontational. Each of us has our own defense mechanisms. Some will even ridicule me. I didn't mean to offend you. I hope you can forgive me and accept my apology. I wouldn't have employed my methods to elicit a response and provoke a conversation with a developer (whom I admire and practically worship for their software prowess and accomplishments), if I thought I had another way. I think that the conversation with a Dev was very productive. I hope that the Devs add the warnings to OCLP that I requested.
Also, the conversation that I regret the most is the one with Jazzzny on Discord. I think he is awesome and the work he does is magical. If he's watching/listening, I'm sorry. I hope you'll forgive me.
SIP is so low on the threat radar compared to the other vulnerabilities, but you know that already.
Last edited:
Sounds like a spill-over from something that happened elsewhere. I loath Discord. It reminds me of a pre-teen MySpace, with less maturity and intuitiveness. The few times I've immersed myself in it I had to take a shower afterwards. Why on earth the OCLP devs decided to associate their brand with it I will never understand.
So anyway can we talk about "Sonoma on unsupported Macs" now? Please?
So anyway can we talk about "Sonoma on unsupported Macs" now? Please?
Dear sir, I really, believe me, REALLY appreciate your comments and points of view. When I says "boring", it´s because to repeate the same speech again and again. So please apologize if you thought I was making fun.
I did, but now I don't. I "unlaughed" your post. Apology accepted. Thank you.
EDIT: We've had a "nice" conversation here. My security concerns about OCLP are no less than they were before this "nice" conversation. It is unsafe for secure activities that require protection of your identity, private credentials and secure data.
Last edited:
Quick question...I have my 5,5 (experimental) computer and installed 1.0.0 which worked well then I installed Sonoma. However, the keyboard and mouse are unresponsive. When it boots up I get a message to install root patches for 1.1. USB legacy patches. However, I have no keyboard or mouse that is responsive. Is there a way or procedure to install on USB or boot up?
… And here is the right one (sorry, should have been in the Ventura discussion: end of semi-OT):
- Avoid listing PCIe FaceTime camera patch on pre-Sonoma OSes
- Only cosmetic in Root Patching UI, however removed to avoid confusion
Last edited:
In addition to seeing the answer to my above question. I came back with a second question. I'm a bit confused with some new settings in Sonoma.
When in system settings: I see an option under wallpaper to show as screen saver, and an option under screen savers to show as wallpaper. Does this do what I think it does? set whatever screen saver is set to also be used as the wallpaper, and whatever wallpaper is set to use a screen saver? Or i is it different from the assumed meaning?
Thanks.
When in system settings: I see an option under wallpaper to show as screen saver, and an option under screen savers to show as wallpaper. Does this do what I think it does? set whatever screen saver is set to also be used as the wallpaper, and whatever wallpaper is set to use a screen saver? Or i is it different from the assumed meaning?
Thanks.
First task of the Fight Club: go and pick a fight with a total stranger. I am sure it goes "deeper" than most people realize.
You need 3 things in order to install the root patches:
1. At least a USB2 or a USB3 hub connected to the MacBook Pro.
2. Connect a wired keyboard to the hub.
3. Connect also a wired mouse to this keyboard or the hub. This way you can access the MacBook and install the root patches.
After that the computer should be usable again normally ...
Good luck!
Last edited:
@TheDebunker If you are still listening, thank you for listening. In addition to the security warnings in the OCLP GUI and when macOS launches with OCLP post-install patches, could you please allow the user to selectively disable post-install root patches? I would feel much safer with my OCLP-patched Sonoma if I could disable Wi-Fi post-install patches and use Sonoma with wired-Ethernet only. My security concerns with OCLP didn't start until I began investigating the root patches for Wi-Fi (I'm not as much concerned about the root patches for graphics). This ability to disable Wi-Fi patches should not interfere with another's desire to keep the Wi-Fi patches enabled. Thank you!
EDIT: @TheDebunker Related to the security warnings in OCLP (GUI and at boot with post-install patches), I think that this statement in GitHub may be misleading:
The statement says that nightly builds are not guaranteed to be safe. Wouldn't the uninformed, unaware OCLP users take this to mean that the official releases of OCLP are guaranteed to be safe? And thus wouldn't they conclude that for guaranteed safety, they should use the official OCLP releases? Just pointing this out. I think it needs to be re-worded.
@rehkram My "general" security concerns all started (albeit a little late) when I started analyzing Wi-Fi patches FOR SONOMA.
EDIT: @TheDebunker Related to the security warnings in OCLP (GUI and at boot with post-install patches), I think that this statement in GitHub may be misleading:
The statement says that nightly builds are not guaranteed to be safe. Wouldn't the uninformed, unaware OCLP users take this to mean that the official releases of OCLP are guaranteed to be safe? And thus wouldn't they conclude that for guaranteed safety, they should use the official OCLP releases? Just pointing this out. I think it needs to be re-worded.
@rehkram My "general" security concerns all started (albeit a little late) when I started analyzing Wi-Fi patches FOR SONOMA.
Last edited:
An old-ish Apple keyboard will also do the trick. The ones that has a built in USB hub. You can tell if it has USB female connectors if it is a Hub. That is what I use for exactly this.