Upgraded only in Spring. Waited long enough. Never have been I saw wrong. Now when I want to reboot my computer I just try to pair my Bluetooth headphones - instant hard reboot
MacOS Catalina: Slow by Design?
621–630 of 1001 posts
Re: MacOS Catalina: Slow by Design?
#622Earlier quoted context omitted.
How about it's totally ineffective? OCSP is pointless if you "soft fail" when the OCSP server can't be reached. [1] This is why Chrome disabled OSCP by default all the way back in 2012-2013 era. Not to mention the performance cost of making all HTTPS connections wait for an OCSP lookup. [2] [1]: https://www.imperialviolet.org/2012/02/05/crlsets.html [2]: https://arstechnica.com/information-technology/2012/02/googl...
That's why there's OCSP stapling and OCSP must staple. Ever seen an nginx server fail HTTPS connection exactly once after rotating the certificate? That's nginx lazily fetching the OCSP response from upstream for stapling purposes.
Notarization has a similar "stapling" workflow as well.
Re: MacOS Catalina: Slow by Design?
#623Earlier quoted context omitted.
It's really very sad, because users have no idea what is going on and there is no incentive for bad programs to improve (actually, there is generally incentive in the opposite direction , because it's work to write well-behaving apps). Users just know that they need to keep buying new computers and that their battery life is worse, but they can't figure out why so they point fingers at everyone but who they should ac…
Remember when shitty user-hostile spying wasn't a library you included that assured you in its readme it was "made with [heart] in California"? Ah, the days when only criminals and bigcos casually engaged in shady crap.
Well, I remember the days when a message in Windows cropped up saying (standard at the time when a program crashed): "Do you want to send the error report to Microsoft" and my boss called me, asking a bit concrened, "Please, tell me honestly, what do you think - should we send them this error report?"
Re: MacOS Catalina: Slow by Design?
#624It seems like there is a lot of confusion here as to whether this is real or not. I've been able to confirm the behavior in the post by: - Using a new, random executable. Even echo $rand_int will work. Edit: What I mean here is generate your rand int beforehand and statically include it in your script. - Using a fresh filename too. Just throw a rand int at the end there. e.g. /tmp/test4329.sh I MITMd myself while rec…
I believe it's just Base64 encoded DER information, based on the code that seems to be similar: https://github.com/apple-open-source-mirror/Security/blob/70...
Re: MacOS Catalina: Slow by Design?
#625I've been forced to update to this pile of shit because latest iOS requires latest Xcode which in turn requires Catalina. It's a nightmare. First off the new apps (music, podcasts, etc) are terrible. They killed off iTunes but replaced it with much worse. These apps don't behave like standard macOS apps, the UI is full of inconsistencies and is just so empty. This website has nice examples of the failures of modern M…
Your experience certainly sounds bad, but none of this is normal; mail sound, USB-C cable brittleness, 1password slowness, all of it works nicely for me.
Re: MacOS Catalina: Slow by Design?
#626Earlier quoted context omitted.
Most vendors have separate engines for detecting malicious scripts. I'd assume notarizing is more about executables, in which case it would be checking the signatures around the shell binary. Also worth noting "echo" doesn't spawn a process but is a routine in the shell itself. If you replaced echo with something that does spawn a process "like scp" it would be interesting to see the results. And if that's doesn't in…
> Also worth noting "echo" doesn't spawn a process but is a routine in the shell itself. In Bash echo is a builtin but /bin/echo also exists if you do actually want to spawn a process.
Maybe OP edited a few times but it doesn't look like they are doing that to me
Re: MacOS Catalina: Slow by Design?
#627Earlier quoted context omitted.
Can you cite any sources for your claim that these things are being implemented to satisfy government/military requirements?
DISA? I don’t know why grand op is downvoted. DoD requirements literally require a timeout setting for screensavers to begin locking. This has caught systems which have a race condition where you can move your mouse quickly and gain desktop access before it locks. The long term effects come from the required changes to the development security model to remain productive and profitable (took MSFT a few OOB hotfixes an…
> This has caught systems which have a race condition where you can move your mouse quickly and gain desktop access before it locks.
I fail to see how this is a race condition rather than how a screensaver is supposed to work?
Re: MacOS Catalina: Slow by Design?
#628Earlier quoted context omitted.
> Also worth noting "echo" doesn't spawn a process but is a routine in the shell itself. In Bash echo is a builtin but /bin/echo also exists if you do actually want to spawn a process.
Maybe OP edited a few times but it doesn't look like they are doing that to me
I'm not sure I understand?
Re: MacOS Catalina: Slow by Design?
#629It seems like there is a lot of confusion here as to whether this is real or not. I've been able to confirm the behavior in the post by: - Using a new, random executable. Even echo $rand_int will work. Edit: What I mean here is generate your rand int beforehand and statically include it in your script. - Using a fresh filename too. Just throw a rand int at the end there. e.g. /tmp/test4329.sh I MITMd myself while rec…
What happens if you edit /private/etc/hosts to point ocsp.apple.com to 0.0.0.0 and flush the DNS cache?
Re: MacOS Catalina: Slow by Design?
#630Earlier quoted context omitted.
I've been seeing the trajectory of Windows (pre-2012 or so) -> Mac (2012 - ~2019 or so) -> Linux (~2018 - now) play out with quite a few people without any issues. And I don't mean developers. They're all pretty educated people but it's taken me by surprise. They come to me in frustration over Mac, they don't want to return to Windows and they really, really, really want linux. I've been using linux since about 1997…
I recently _really_ tried adopting Linux on a hobby development machine that I built back in 2016 (hardly new hardware -- and desktop not laptop). Sleep never worked, graphics sometimes borked, UI felt janky and inconsistent, icons are super fugly and often too theme-y to the point of being undifferentiated at a glance, HiDPI support is a giant mixed bag (in 2020), machine would randomly freeze (mostly elementOS; Ubu…
See, that's the response I was used to and the one I expected to get from everyone.
The crazy thing is that I haven't heard it yet from the people I helped. Times may actually be changing now, just not swiftly. Perhaps it's the "decade" of desktop linux.
It's also not because linux is so great but because windows and apple are constantly stumbling over their own shoelaces and shooing customers away.