News for hackers. Stuff that matters.
Re:Mac OS Catalina: more trouble than it’s worth (Part 2) by mikenew on Friday February 14, 2020 @02:39AM (#22324718)
One thing that drives me nuts is the way you get a security popup when you're working in a terminal. So you're ssh'd into a mac, you try to do something (like xcodebuild or whatever), and then it just sits there doing nothing while it waits for you to put in a password on a window you can't see.

It's not exactly new in Catalina, but it's worse. Apple just does not even think about the fact that you might want to do things remotely or automatically.

Re:Mac OS Catalina: more trouble than it’s worth (Part 2) by htfu on Friday February 14, 2020 @05:23AM (#22325406)
Yup. Or even just popups originally appearing behind other windows and missed. Or accidentally clicking the wrong option, or as with Mojave when apps requesting to record sound couldn't successfully trigger the popup in many cases.

The execution is where Apple is fucking up, yet people are hating on the concept, as if poor UX is somehow mandatory for something like this. Worries me a bit.

Re:Mac OS Catalina: more trouble than it’s worth (Part 2) by nomel on Friday February 14, 2020 @01:33PM (#22328916)
This is like having a firewall and getting upset that it's not passing everything through.

I believe there should absolutely be intentional, physical, steps to allow full remote access. Intentionally setting the terminal for full disk access is no less crazy than intentionally exposing a port through your firewall.

Re:Mac OS Catalina: more trouble than it’s worth (Part 2) by mikenew on Friday February 14, 2020 @03:15PM (#22329942)
Yeah a firewall where you open a port, but have to plug a monitor and keyboard into your router every time you want to use it.

I'm not "upset" that it needs authorization. I think it's a design flaw that you can't do it via a terminal, you don't even know that that's why your process has stalled, and you have to click a box every time.