Comment by chronogamous

2 hours ago

I still can't figure out how to set Sequoia's firewall to enable logging.

I've also spent quite a bit of time trying to figure out how to properly configure which DNS-server should be used, but while reading this thread I'm beginning to wonder: maybe the reason I'm having so much trouble understanding how to set this up properly could be that the OS is messing with me and my DNS-settings, and the lack of documentation describing how DNS-resolution is supposed to work on MacOS is really a feature meant to keep me from finding out that they are deliberately making it impossible to secure connectivity at a DNS-level?

Next thing you know, a similar explanation might pop up regarding configuration of the packetfilter. It has already been frustrating not being able to figure out these basics on my own for several years. It will be absolutely infuriating to find out this struggle has been pointless anyway, and it turns out they have been using mislabeling core components of their OS. The moment DNS-settings are not really settings the OS uses when doing DNS-lookups, I feel deliberately deceived.

It's like calling an OS Unix-based, and subsequently override standard Unix-rules seemingly at random and without consent of whoever is supposed to be the system's administrator, that people might start thinking the OS is merely intended as a tool to ruin any reputation of reliability that Unix may have once had. The great thing about a Mac is that it just works, they said. So far my experience has been the opposite. And whenever I get the illusion that something works as it is expected to work, I've learned to recognize it for what it is. An illusion. How is any of such behaviour even legally and ethically justified? How can they legally sell systems running MacOS to customers whose job includes working with classified information? How are such customers supposed to secure their system if it these 'features' are not properly documented?