Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Don’t get me wrong, I’m glad Apple addressed a security flaw with a new update, but as others said on the iOS 14.5.1 post, didn’t Apple discover this over the two months of the beta? I made a clean install hoping 11.3 would last a while... I could have waited a week before making this clean install
These fixes are in WebKit, which itself is upstream from Apple. It may be that WK was updated after 11.3 shipped.
 
Wow. Integer overflow?! That should be prevented from a low-level OS security protection. We looked at that in my 2009 hacking class. Wouldn't have thought we would have such a "basic" exploit today.
Nope. Maybe you’re thinking of stack or buffer overflows, but integer overflows can’t be prevented by the OS.

it can be prevented by the compiler, but unfortunately WebKit wasn’t written in a safe language like Swift.
 
So... there is still no reason to bother with Big Sur, then, unless you're forced?
 
Apple, shape up! Every recent updates have been followed up by .1 release about a week later.
🎼They better shape up
They better understand
To our heart we must be true
Nothin' left, nothin' left for us to do🎼
 
meh, still not worth updating and losing all of my sideloaded apps.

i’ve taken a bite of the forbidden apple and now I don’t want to let go! 11.2.3 is where i stay
 
Big Sur 11.3 appears to have corrupted my 4TB G-drive:


I learned a big lesson. I am going to get the drive replaced under warranty, but will get a separate external drive just for my M1, because it looks like there are some serious issue with Big Sur and M1 Macs where it likes to corrupt external devices.
Any other sources for your claims of the OS corrupting external drives other than citing your own post?

Your other post sounds more like a hardware problem.

Agreed. This definitely sounds like a hardware fault. Big Sur didn't cause your external drive to start making strange noises.
 
  • Like
Reactions: TiggrToo
A bug in WebKit wouldn't be such a big deal if it weren't for the fact that Apple prohibits iOS browsers from using another engine.

WebKit/Safari is the new Trident/Internet Explorer. There's already precedent for Microsoft being found guilty of making a monopoly via IE - it's time Apple is found guilty of an even more extreme version of this with WebKit + the App Store.
 
Apple, shape up! Every recent updates have been followed up by .1 release about a week later.
I would call what they are doing is shaping up since they recognize and issue and fixed it within a week. If this were Microsoft you can count on a fix after 60 days or never.
 
  • Disagree
Reactions: Anthony Sullivan
Well damn, it got rid of my Hello screensaver. Now I have to reinstall it on my Intel MacBook Pro.
 
And folks complain Windows has a lot of updates. Looking in the mirror.
If you ask me it technically does, the reason why people like the way macOS updates is cause it's just a single update altogether rather than multiple updates split up into various different things
 
  • Like
Reactions: saynotosync
Nope. Maybe you’re thinking of stack or buffer overflows, but integer overflows can’t be prevented by the OS.

it can be prevented by the compiler, but unfortunately WebKit wasn’t written in a safe language like Swift.
It sounds like it’s time for a rewrite if that’s the case. The impact of bugs like these is always surprisingly big.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.