111–120 of 322 posts
You know, this is a pretty apt analogy. Vista (apparently) was considered terrible primarily because it ripped off the band-aid and made a bunch of inconvenient but important-for-security-in-the-long-term changes. [0] [0]: https://twitter.com/swiftonsecurity/status/85185740489147187...
I for one am super happy for these permission dialogs. They help me know which apps are doing what and tell them, no, you can't do that! Going from the old model, a native app can do almost anything to the new model, a native app has to ask permission means that yes, there is a one time issue of having to give all apps the permissions you want them to have. That happens just once though on this transition. Normally i…
Seeing some people say 'if you were fine with it before...' - well that's the thing, I wouldn't have been fine with it before if I had known.
Earlier quoted context omitted.
FWIW, every program looks like one that usually is set to start at startup; the intent is to have the dialogue only show up when you start an app for the first time. Since so many background apps were running at startup they all slowly needed to ask for their permissions. > create a migration UX Might not be possible if the previous MacOS isn't full-on tracking what folders a program is accessing, and it still would…
If you were ok running your previous apps you should also be ok with gathering usage data for a week before the OS attempts to do a hard cut-over to a more secure model.
I'm astounded with some of the user security dialogs that Macs display. I got one today: "VSCode wants to make some changes. Deny or Allow." That was the exact wording. Seriously? THIS. BENEFITS. NO. ONE. The only thing I can figure is that, somehow, Mac has required applications to display something to the user to get their permission to make some substantial system-level changes. But the application is, I guess?, a…
Earlier quoted context omitted.
These are all new permissions. So there is no database of applications that need access to read/write Documents or Pictures. So a UI like you are suggesting is not technically possible to create.
Maybe we have different understandings of how that UI would work, but I imagine it to be totally possible: Take all the windows/notifications from OP's screenshot, map each of them to a row in a table, group by application. Show all this info in 1 modal, call it Migration Assistant.
I'm astounded with some of the user security dialogs that Macs display. I got one today: "VSCode wants to make some changes. Deny or Allow." That was the exact wording. Seriously? THIS. BENEFITS. NO. ONE. The only thing I can figure is that, somehow, Mac has required applications to display something to the user to get their permission to make some substantial system-level changes. But the application is, I guess?, a…
So you want all your apps to have root-level system access?
So users almost always click "allow". What's the point of the dialog then?
Really, the dialog should be explicit about what's needed and why it's needed and what click "allow" does (i.e., always allow this action, for this purpose? Or always allow any root-level action from this app? Or something else?)
Only then will users actually be able to make a decision beyond "do I trust Microsoft and do I want to do this thing I just asked Word to do?"
I'm astounded with some of the user security dialogs that Macs display. I got one today: "VSCode wants to make some changes. Deny or Allow." That was the exact wording. Seriously? THIS. BENEFITS. NO. ONE. The only thing I can figure is that, somehow, Mac has required applications to display something to the user to get their permission to make some substantial system-level changes. But the application is, I guess?, a…
They haven't quite descended to Microsoft levels of "We're restarting your computer now kthxbye", but it's a grim, user hostile path they're on, at least with notifications.
Earlier quoted context omitted.
If you were ok running your previous apps you should also be ok with gathering usage data for a week before the OS attempts to do a hard cut-over to a more secure model.
It seems like this would be very difficult to implement securely. You basically would have to preserve the old, unsafe mode and hope that nobody circumvents whatever restrictions you put in place to make sure that it only applies to the pre-migration apps .
Earlier quoted context omitted.
Apple could have figured out a way to coalesce all the individual pop-ups into a single window. I'm sure they considered it and deemed it not worth the effort since this is a one-time pain... of course it's one-time pain shared by millions of users. :-(
An individual window would have completely destroyed the point. The point was to make you aware of what permissions the applications you use require access to. And to get explicit permission from the user.
Hardly. Apple could have used the OSX installer to scan two or three common locations for applications and do a bit of static analysis. Apple could have put the permissions notifications in the notification center with an annoying nag screen every hour or two for the first ~30 days turning into an immediate prompt after that (or after all detected programs have been processed).