Apple security patch update breaks file-sharing 🤣
seriously, whatever happened to this company's quality standards, they aren't the same. https://t.co/c1pxxggp0y?amp=1
This was probably the result of an engineer telling their manager, he we need to unit test this. And the manager says no let's get the patch deployed then we'll focus on testing. That's basically what every shitty middle manager ever has said during a regression after a deployment
This is accurate.
That's what happens when you invest in new animojis and not security.
A buddy of mine who works in IT security actually had a good point on this: when you consider how slow the average person is to update their phones / computer software, you need to design methods like this to improve adoption rates. So it’s not a quite fair comparison to say one was prioritized over the other.
So they expose millions of users to a security vulnerability. For what? For improving adoption rates? That’s irresponsible at best.
Where are the Apple employees on these threads 😂? 🤫
Busy bathing in piles of cash
^ pretty much.
I won't know. They had an odd SMB implementation for years.
Hello hello.
Apple also loves to break square. Last year 10.0 literally broke BLE. This year Apple broke accessories.
Awww imagine all the street hot dogs that went uneaten...
You can be an ignorant dick all you want. Some people actually live paycheck to paycheck. Not being able to take payments is very important to people trying to make a living.
Last good Apple product was: MacBook Pro 2015
My favorite. I don’t know what I’m gonna do when my current one gets too old. I don’t want to carry around 15 dongles lmao
The current MacBook is an abomination. Screw the keyboard. Apple needs to stop making cosmetics instead of real useful hardware.
Anyone knows how Linux handles root pw setup?
https://www.aychedee.com/2012/03/14/etc_shadow-password-hash-formats/
Thanks, but I'm interested in a basic experience explanation: how is root password set for the first time on a new Linux OS? How do they deal with this dilemma: "If we leave the password blank and user doesn't override it during the setup anyone can override it should they get access to the settings"?
Possibly a quick fix to stem the bleeding while they work on a more complete patch?
there shouldn't be a "more complete patch", it should fix the exploit without breaking anything else. setting a password for root was a better fix