Mostly off-topic: have Apple and Microsoft completely given up on non-trivial changes to desktop operating systems? Will MacOS look basically the same in 40 years? Or is the idea that everything will be AR/VR by then and there is no use innovating in this domain?
Apple’s macOS Ventura – New Security Changes
151–160 of 193 posts
Re: Apple’s macOS Ventura – New Security Changes
#152> However, the Gatekeeper check here is overridable by users. This is presented as a flaw, but I'm not sure they are thinking through the alternatives. It's hard to give too much credence to security experts who are't thinking holistically. Perhaps there is a flaw, but I'm curious to know what it is.
Things the user can override are things social engineers can convince users to override.
Re: Apple’s macOS Ventura – New Security Changes
#153Re: Apple’s macOS Ventura – New Security Changes
#154Earlier quoted context omitted.
I can picture a big cat in my mind. That helped to peg OS X releases and enabled me to mentally distinguish and order them. I can't picture "Monterey" or "Ventura" or any other macOS names, they have no meaning to me.
Ventura has a meaning to me.... Ace Ventura, a cartoon from my childhood about a egotistical questionably competent detective. I'm not sure that's the image Apple wants to give off though...
Re: Apple’s macOS Ventura – New Security Changes
#155And for consumers I don't think it's a good idea to remove this option altogether. The owner should have full control if they desire it.
The constant check for modifications is great though. I'm surprised that wasn't the case before.
Re: Apple’s macOS Ventura – New Security Changes
#156Somewhere between Mountain Lion and High Sierra, it became impossible to delete or even mark non-executable various annoying built-in applications which I never use, e.g. iTunes.app and Safari.app, which often open without me asking them to. Does anyone know how to re-enable this functionality?
Re: Apple’s macOS Ventura – New Security Changes
#157Lets hope the open core project, namely the Open Core Legacy Patcher[1] will revive some older models to run Ventura. Personally, I'm running a 2014/15 Macbook Air 11" for 7 years now[2] and with "Open Core Legacy" on Monterrey with no issues at all. [1] https://dortania.github.io/OpenCore-Legacy-Patcher/MODELS.ht... [2] Except the mainboard, display and shell everything else thats modular (wifi card, ssd, battery an…
But it involved a lot more than just firmware. And there were lots of known issues with some configurations.
I'll check that software out though, perhaps I can run Mojave on my 2010 mbp, I really miss the dark mode
Re: Apple’s macOS Ventura – New Security Changes
#158Nothing terribly major here, it sounds like. Making login items visible is a long-overdue change... but none of these are going to have any particular impact on average users or average apps. On a pettier note, can we get a better source than a website that's using JS to change its title when it doesn't have focus to try to gain attention? (It toggles about every second between "macOS Ventura | 7 New Security Changes…
Re: Apple’s macOS Ventura – New Security Changes
#159At least two other security changes: - userspace filesystems: the nail on the coffin for kernel extensions. Now we won't need to run in "reduced security" to use FUSE and that was the last kernel extension that remained popular. Probably kexts will be deprecated shortly - rapid security response - it seems also to include changes in Xprotect and mrt
> the nail on the coffin for kernel extensions The OpenZFS implementation on macOS also requires kernel extensions, and I don't suppose it can easily be ported to FUSE or that that would have desirable performance characteristics. Special kernel extensions are also required to get some basic functionality working on macOS these days, like disabling pointer acceleration.
Could you point me to the kext that does that? I’ve been trying to find a way to disable it for ages.
Re: Apple’s macOS Ventura – New Security Changes
#160Most concerning is Gatekeeper, as I do still routinely run into scenarios where it harassess me about applications I am trying to run and on the odd occasion I have to manually codesign things. It will be super annoying if this now starts making developer's life hell because it is nannying binaries they are building, sharing or working with as part of their development work.
You can completely disable Gatekeeper if it annoys you: $ sudo spctl --master-disable