OPs log screenshot clearly shows that they _did_ in fact, authorize the installation _non-interactively_.
/s
I wonder if it was a sudo permission thing and they were within the elevation timeout so it just automatically accepted for them in the background? That's what the log suggests to me.
This happened to me and I definitely had not authorized anything recently. I also looked at the logs on my machine and saw similar stuff. Even if I had, it still shouldn't have tried to upgrade me, because installing security point release updates requires a password authorization prompt every time. (It won't even accept Touch ID for it!) I ranted about it on Mastodon. Infuriating.
Yeah, it's probably just some user experience thing, like the keyring is unlocked because you're logged in so it's trying to be helpful by not making you enter a password again, but it's a little sketchy when the user has clearly toggled all of the update switches off.
Comments
OPs log screenshot clearly shows that they _did_ in fact, authorize the installation _non-interactively_.
/s
I wonder if it was a sudo permission thing and they were within the elevation timeout so it just automatically accepted for them in the background? That's what the log suggests to me.
This happened to me and I definitely had not authorized anything recently. I also looked at the logs on my machine and saw similar stuff. Even if I had, it still shouldn't have tried to upgrade me, because installing security point release updates requires a password authorization prompt every time. (It won't even accept Touch ID for it!) I ranted about it on Mastodon. Infuriating.
Yeah, it's probably just some user experience thing, like the keyring is unlocked because you're logged in so it's trying to be helpful by not making you enter a password again, but it's a little sketchy when the user has clearly toggled all of the update switches off.