So you do have it as well...no way to disable incoming connection through terminal ?Posted on Reddit that it’s been that way on macOS15 (Sequoia) early beta?
is exclusively to this OS can’t be turned off .
Last edited:
So you do have it as well...no way to disable incoming connection through terminal ?Posted on Reddit that it’s been that way on macOS15 (Sequoia) early beta?
is exclusively to this OS can’t be turned off .
just checked again, see it only on the OCLP MacBook Firewall, the native M1 does not show it.look here it is , it's so weird like the classroom app services preinstalled ... I mean why is it so ultimately I don't think apple dev would let this configuration purposelessly.
I was just checking this thread now , and went to open it with BBEdit. I am running and old 9.1 with oclp sequoia , I know didn't have it on Sonoma . I don't know much what to think, if I should be too much concerned after reading this https://eclecticlight.co/2020/08/20/the-vulnerability-in-remote-login-ssh-persists/ & https://threatpost.com/xcode-macos-malware-apple-developers/164897/. thx for your helpApples official answer: https://discussions.apple.com/thread/3066623?sortBy=best
Seems its not only Sequoia related
So you do have it as well...no way to disable incoming connection through terminal ?
I was just checking this thread now , and went to open it with BBEdit. I am running and old 9.1 with oclp sequoia , I know didn't have it on Sonoma . I don't know much what to think, if I should be too much concerned after reading about Trend Micro on XCSSET malware vulnerability in Remote Login (ssh) &Apples official answer: https://discussions.apple.com/thread/3066623?sortBy=best
Seems its not only Sequoia related
Didn’t read your previous post. Just in caseFor MBP 14.3 (2017) nothing has changed.
Screen brightness is not adjustable.
After waking up, the screen backlight does not turn on.
There is a problem with obtaining permission to run some applications. The system does not accept the administrator password, but Touch ID works.
have you tried booting into safe mode, trying to patch there and finish in normal mode, thought I read something about that workaround in earlier posts ...My wifi connection longer working. I don't have access to a wired connection. [I do, however, have non-OCLP volumes set-up on the laptop.] Would you kind readers please give me advice for getting my wifi connection (in the Sequoia environment) up-n-running? Thank you!
Some observations for those planning to use Time Machine for Migrating from Sonoma to Sequoia soon FWIW.
I test-migrated two rMBp 10,1 and in the end they appear to be working after some workarounds that are to be expected at this time, as the patches are clearly marked by the devs as a preview. A very polished and useful preview I might add.
A small warning that might save some time for some:
Today's OCLP 2.0n does not work when using Migration Assistant and can bork the receiving Mac in the migration.
Downgrading to stable OCLP 1.5 for MA still works as expected. So migrating a Sonoma install to another Sonoma install and then upgrading that install to Sequoia using OCLP 2.0 and the terminal appears to have worked. The upgrade in System Settings stalled and came and went. Terminal worked first time. Again, FWIW, YMMV.
FYI: I think the 'safe mode' approach doesn't work for me (to restore wifi functionality). MBA 2014.have you tried booting into safe mode, trying to patch there and finish in normal mode, thought I read something about that workaround in earlier posts ...
... yes, was discussed here
I hear you. Keeping the versions of stable OS and OCLP the same has however worked well for a long while here.Just a heads-up that I have seen consistent issues (over many years) with Migration Assistant even with older revisions of OCLP. I no longer even bother with it unless I have a very good reason to make the attempt. I always go in assuming I will be starting fresh and manually moving data.
FYI: I think the 'safe mode' approach doesn't work for me (to restore wifi functionality). MBA 2014.
Do you kind readers know of a way to restore wifi functionality, for MBA 2014, that does not require Ethernet connection? Thank you in advance!
Just to offer an alternative view, after I learned the proper way to migrate, I can't remember ever having issues with Migration Assistant. Migration must be performed from the source to the destination BEFORE applying OCLP post-install patches to the destination.Just a heads-up that I have seen consistent issues (over many years) with Migration Assistant even with older revisions of OCLP. I no longer even bother with it unless I have a very good reason to make the attempt. I always go in assuming I will be starting fresh and manually moving data.
Start in safe mode perhaps?Help! I was happily running 14.6.1 with Opencore 1.5.0 on my 2015 Macbook Pro - for months. Yesterday, I saw the Opencore 2.0.0 upgrade & installed it then I downloaded Sequoia onto USB installer. The install seemed to be going fine, until the final boot, where it got stuck.
I tried reinstalling, but it always gets stuck at the same point. In verbose mode, the failure seems to be "AppleKeyStore" operation failed. Any ideas?
Thanks.
In the scenario that I do get this work, what are the next steps? Is there a verified method for restoring wifi functionality, so long as the user has got a wired connection (or, perhaps, a Internet Sharing workaround) in place? Obviously I've not been following this thread so closely. I appreciate your kind advising very, very much!Only thing I could think about is LAN internet sharing between two Macs - if a second one is available .. but never tried it myself yet. But it is well described https://support.apple.com/en-gw/guide/mac-help/mchlp1413/mac#:~:text=Connect a standard Ethernet cable,computer name for each computer.
View attachment 2419727
In the scenario that I do get this work, what are the next steps? Is there a verified method for restoring wifi functionality, so long as the user has got a wired connection (or, perhaps, a Internet Sharing workaround) in place? Obviously I've not been following this thread so closely. I appreciate your kind advising very, very much!
Ah. Rats!I think the patcher needs Internet to load support files ...