Joer293

Ive worked for multiple cloud providers and security red/blue teams. Rotating certs for some systems is entirely hands off and flawless.  Like Microsoft AD and desktops. MS solved the desktop rotation headache decades ago. But, That is not the case for big businesses at all. They cant use lets encrypt or free tools to rotate because those all violate some other security compliance issue for their regulated work loads. certs for business critical apps are labor intensive, the change to 1 year mark for TLS has led to an industry wide increase of outages related to cert rotations. Sacrificing Availability for almost no gain of confidentiality isnt worth it for business.. Sure, changing 1 system is easy. Synchronization of changing certs on 100,000 servers of 100 different functions isnt easy, and automation would need changes every single rotation, making it not as helpful as executives think. Most internet infrastructure requires 30+ day notice for downtime and have dictated maintenance windows per customer contracts. Rotating certs on 24/7 apps requires downtime. Often its kept to a 60 second cut over, but worst case with banks mainframes, dozens of teams, it can be several hours. There are set maintenance windows too. 45 days really means 30 days + 15 grace period. Just like 13 months is 12 months + 1 month grace period. This will be a nightmare for security. Outside of researchers, nobody is breaking certs besides governments. Hackers have 1,000 ways to break in, certs dont even make it on that list of things to try. Like rekeying your front door monthly, when that effort distracts you from closing windows. 

Only telco execs(and politicians/lawyers) believe their network is secure. Everyone else doesn’t care.  customers use TLS websites and businesses use vpns.  

This is almost identical to what occurred to Microsoft Windows decades ago when they were the dominant monopoly. Regulation forced Microsoft to do all of this. They fought it hard, played all the same tricks all your comments are saying apple and Google will attempt. History repeats itself. 

I have the latest update beta and it does not fix the issues with battery or gps. <begin rant>. Yes I’m very familiar with apples default response of wipe and load the watch. It’s a gamble of your time if that even works for the specific issues. It’s just a way for Apple to get you out of the store or off the phone most times.  This is not at all simple or short unless you are someone who barely uses the watch for anything. It can take a couple hours for backup and restore, if it works successfully the first time. plus 2 - 7 days for banks to revalidate the “it should be instant” Apple Pay. Plus phone calls where the banks blame Apple and Apple blames the banks. Plus COVID wait times. And don’t forget carriers that are unable to process activation on cellular and “nobody else has this issue” reported by many people. Then there are always apps that need to be reconfigured, data lost, etc. wipe and load should be a last resort. Oh and there is no way to validate a backup is good. I’ve had it happen twice where iTunes says the backup was corrupted, must start over as new watch. Especially on upgrading to a new watch restores are unreliable <end rant> 

I haven’t played games, but the line glitches appear, under idle conditions. 27” 10core i9, 128gb and 16gb 5700xt. I have not seen the tearing others have.
on pc’s I’ve owned this was a spread spectrum/clocking/voltage fix. No idea how to test that on an iMac.