41–50 of 176 posts
Honest question: is this evidence of worsening QA at Apple, or a consequence of OS X growing a longer tail of old and varied hardware? E.g., how does this compare to the rate of equivalent problems with large Windows releases?
Honest question: is this evidence of worsening QA at Apple, or a consequence of OS X growing a longer tail of old and varied hardware? E.g., how does this compare to the rate of equivalent problems with large Windows releases?
Ok since these types of threads are typically filled with complaints, just to add another data point: I’ve upgraded last week and have not experienced any problems at all. And yes, I’m using USB hubs, printers and even Java.
Is that on an M1? Apparently the Java issue only affects Apple silicon for some reason
> Write XOR execute (W^X)
> Apple Silicon Macs will enforce a restriction called “write XOR execute” (W^X). This means that chunks of memory will be designated as writable, or as executable, but never as both at the same time. Many macOS apps contain performance optimization programs that require memory to be both writable and executable, but this can lead to serious security issues. By enforcing W^X, Apple will harden Mac security at the memory level. App developers, however, won’t be left out in the cold — if they still need those optimization programs for their apps, they can use a new macOS API that provides a way to switch between write and execute permissions quickly and safely.
And the nature of W^X - https://en.wikipedia.org/wiki/W%5EX
> W^X ("write xor execute", pronounced W xor X) is a security feature in operating systems and virtual machines. It is a memory protection policy whereby every page in a process's or kernel's address space may be either writable or executable, but not both. Without such protection, a program can write (as data "W") CPU instructions in an area of memory intended for data and then run (as executable "X"; or read-execute "RX") those instructions. This can be dangerous if the writer of the memory is malicious. W^X is the Unix-like terminology for a strict use of the general concept of executable space protection, controlled via the mprotect system call.
---
See also Porting just-in-time compilers to Apple silicon - https://developer.apple.com/documentation/apple-silicon/port...
And W^X now mandatory in OpenBSD (8 years ago : https://news.ycombinator.com/item?id=11789169 )
My upgrade to Monterey (MacOS 12.x) broke my Canon D530 printer driver. Re-installing the driver didn't help. Now I have to print to a PDF, copy that to an old Snow Leopard 10.6 machine, and print from there. FYI, Snow Leopard is 11 major OS revisions behind Monterey. Printing worked fine in Mohave, 3 major revisions ago. I also can't write any files to /, even with SIP disabled, and during the Monterey upgrade, Appl…
nc your_printer_ip 9100 Wait what? So 10 screens of bangers like "An app may be able to execute arbitrary code with kernel privileges" and "An attacker with arbitrary kernel read and write capability may be able to bypass kernel memory protections. Apple is aware of a report that this issue may have been exploited." are not considered smoking guns?