11–20 of 89 posts
What an absolutely amazing tour-de-force of a devastating design flaw in all versions of macOS and iOS and tvOS and watchOS!
The negotiations detailed in the bug report timeline about meetings between "senior apple and google leadership" for keeping this secret past the general deadline really underlines that.
Copying my comment from the earlier submission that didn't gain much traction here: What an absolutely amazing tour-de-force of a devastating design flaw in all versions of macOS and iOS and tvOS and watchOS! The negotiations detailed in the bug report timeline about meetings between "senior apple and google leadership" for keeping this secret past the general deadline really underlines that.
I wonder what other fallout we might experience from this.
Ever since installing 10.12.1, I've been having a bunch of processes randomly entering a quasi-paused SIGSTOP-ish state (neither closable, apps not "bouncing" (loading) and just not responding. Running Instruments, correlating logs and such doesn't identify any clear cause. I'm having to `sudo kill -CONT -1` in order to get things moving again. I'm wondering if it's related to XNU mitigations or just some spurious "s…
Nice use of -1 there.
/* must be run as root */
#include
main(){for(;;){kill(-1,SIGCONT);sleep(10);}}
“Considered Harmful” Essays Considered Harmful -> http://meyerweb.com/eric/comment/chech.html
The sad reality is that black hats have been exploiting this class of bugs for years .
Earlier quoted context omitted.
Thx. For an encore: /* must be run as root */ #include main(){for(;;){kill(-1,SIGCONT);sleep(10);}} and a .plist. Temporary hackaround.
What does -1 do, send that signal to all processes?
-1
All processes with pid larger than 1 will be signaled.