Live data from Hacker News

About the security content of macOS Tahoe 26.6

support.apple.com

81–90 of 157 posts

Re: About the security content of macOS Tahoe 26.6

#81
post #61
post #37

Earlier quoted context omitted.

> For context, there have been issues with MacOS 26 which have led many people to defer upgrading For me the issue is liquid glass. Which I doubt is getting fixed any time soon

macOS 27 does polish Liquid Glass and makes it look passable on macOS IMHO. It was very bad on 26. Comically bad.

That's the sad thing: Apple decided to leave all Intel macs on broken macOS 26. Very bad on Apple's part.

Re: About the security content of macOS Tahoe 26.6

#82
post #48
post #41

Earlier quoted context omitted.

> this is better than nothing. Having installed the beta, I think that's the best you can say about it.

I hear it’s slower? Can you comment on that?

The 27 betas? No, they are generally faster than 26.

Re: About the security content of macOS Tahoe 26.6

#83
post #76

Earlier quoted context omitted.

Did they un-hardcode the corner radius? I mean were they able to? I mean not that that anyone at this point needs convincing how utterly disgusting incompetent they’re at software.

They reduced the radius back to older, smaller size and now all apps use a single radius, vs the weird 3 different radii in Tahoe. Looks better.

I was shocked to find out the inconsistent corner radii in Tahoe was an intentional design decision. I figured it's so obviously bad that it was just sloppy work. But one of the WWDC session videos bafflingly clarified that it depends on whether the app has a toolbar or not.

https://youtu.be/VqTn9NgiE1s?t=439

I can't imagine how the people who signed off on that were put in charge of design at Apple.

Re: About the security content of macOS Tahoe 26.6

#84

Earlier quoted context omitted.

> high ranking Apple employee Jony Ive basically works for Open AI (it's more complicated, but it's a good approximation), and has more or less rebuilt a designing team over there. He's not the central person mentioned in Apple's accusations but that's arguably the central point that's triggering all of this.

Didn't he live Apple a very long time ago?

Yes, the high ranking employee at the center of the accusations is not Ive, but Tang Tan, former VP of product design

https://www.bbc.com/news/articles/cy8w379e091o

Re: About the security content of macOS Tahoe 26.6

#85

15.7.8 is out today as well, with these security fixes: https://support.apple.com/en-us/128071 . For context, there have been issues with MacOS 26 which have led many people to defer upgrading until MacOS 27 is available, and MacOS 15 is the previous version.

Same thing happens almost every release. I've stopped updating my Mac machine until I see something in the release notes I literally have to have in order to continue doing macOS/iOS builds, otherwise I'm staying on the version I've validated to work, and I know the existing bugs with.

A better strategy would probably be to stick with the previous *major* release, but, do install its ("minor") security updates...

Re: About the security content of macOS Tahoe 26.6

#86
This may be a naive take, so if anyone has insight please feel free to share, but across Windows, Mac, and Linux OS's I see many cases of path parsing vulnerabilities resulting in sandbox escapes, code execution, or data access issues. When presenting the user with a file picker or command-line input, is it really needed that the software can handle the full POSIX spec?

I do not see a "typical" user needing to access a path with say a network storage but multiple ../.. and hard and soft symlinks simultaneously. I think "be liberal in what you accept" might need to be revisited for path parsing with some sort of OS-wide single-implementation as an optional feature.

Re: About the security content of macOS Tahoe 26.6

#87
post #20
post #3

Weird thing to see at number 3 on HN - is there some subtle context I am missing here? Are we wink winking that it's a lot of fixes?

I think it's because it's the first big batch of fixes found at Apple by Mythos.

Is this speculation? Where does it say Mythos was responsible for any of this?

Re: About the security content of macOS Tahoe 26.6

#88
post #37

Earlier quoted context omitted.

> For context, there have been issues with MacOS 26 which have led many people to defer upgrading For me the issue is liquid glass. Which I doubt is getting fixed any time soon

Also a liquid glass hater, but for what it's worth, 27 is supposed to make it a little bit better. I would prefer to go back to what I had before I had to upgrade into this horrible UI, but this is better than nothing. https://www.cultofmac.com/news/liquid-glass-changes-ios-27-m...

macOS 17 is decisively faster on my MacBook Air M1 16 GB than macOS 26/27 is on my MacBook Pro M2 Max 32 GB. And I don’t mean just the animations themselves but lag/sluggishness/responsiveness in general.

Re: About the security content of macOS Tahoe 26.6

#89
post #79

Earlier quoted context omitted.

I hate the round corners. It's already too much on 15, but way worse on 26. It looks like "Baby's first OS", designed by Fisher-Price.

They reverted this in 27 https://www.macrumors.com/2026/06/09/macos-golden-gate-liqui...

Love to see this, now if only they could revert the whole shimmering oil slick disaster that is "glass" on iOS (unlike macOS, even if I "reduce transparency", the oil slick effect still appears in many places, in addition to all the spacing issues).

Re: About the security content of macOS Tahoe 26.6

#90
post #41

Earlier quoted context omitted.

> this is better than nothing. Having installed the beta, I think that's the best you can say about it.

As long as the UI improves and I can ignore all the AI stuff they're starting to push through, that's fine with me, though like many longtime macOS users, I'm not holding my breath for a bug-free experience.

> though like many longtime macOS users

For those of us older than just 10 years of using macOS, the older Apple OSes have instilled within us the desire to never install the X.0 release and wait until at least the X.1 release. The bug-free experience is a myth

Post reply on HN