0x0@programming.dev
on 11 Oct 2024 14:08
nextcollapse
Next version: admin privileges will be subscription-walled.
jacksilver@lemmy.world
on 11 Oct 2024 14:40
nextcollapse
To be honest, it actually does sound like a reasonable and security focused change. It basically looks to take a more zero trust kind of approach in regards to admin elevation.
UAC is a bandaid for a lack of proper local user account management. I never see it in Enterprise, nor on my home machines, as users have appropriate permissions, with admin being tightly controlled. (To be honest, I just turn it off on my home machines, run as a user, and if I need admin I switch accounts).
This really only affects home users who like to run as admin all the time (about 98% of us, I’ve been guilty of it most of my career).
I get it, I just don’t see it really being a significant risk (this is related to a hack published perhaps a week ago where an attacker, could, potentially, maybe, gain admin by timing the attack perfectly during an install, but only on specific machines).
jacksilver@lemmy.world
on 11 Oct 2024 18:03
collapse
I’d take your word on it, OS level security is not my forte. The main thing I was calling out is that the change seems to be looking to actually fix an issue and not limit control, as the original commenter seemed to imply.
Hamartiogonic@sopuli.xyz
on 11 Oct 2024 17:27
collapse
Some wise Lemmy user once said something like this: “Windows is an enterprise OS with consumer features. MacOS is a consumer OS with enterprise features.”
If that’s really the case, MS doesn’t really care that much about the consumer market. My guess is, most of the money comes from various companies anyway.
threaded - newest
.
Next version: admin privileges will be subscription-walled.
To be honest, it actually does sound like a reasonable and security focused change. It basically looks to take a more zero trust kind of approach in regards to admin elevation.
UAC is a bandaid for a lack of proper local user account management. I never see it in Enterprise, nor on my home machines, as users have appropriate permissions, with admin being tightly controlled. (To be honest, I just turn it off on my home machines, run as a user, and if I need admin I switch accounts).
This really only affects home users who like to run as admin all the time (about 98% of us, I’ve been guilty of it most of my career).
I get it, I just don’t see it really being a significant risk (this is related to a hack published perhaps a week ago where an attacker, could, potentially, maybe, gain admin by timing the attack perfectly during an install, but only on specific machines).
I’d take your word on it, OS level security is not my forte. The main thing I was calling out is that the change seems to be looking to actually fix an issue and not limit control, as the original commenter seemed to imply.
Some wise Lemmy user once said something like this: “Windows is an enterprise OS with consumer features. MacOS is a consumer OS with enterprise features.”
If that’s really the case, MS doesn’t really care that much about the consumer market. My guess is, most of the money comes from various companies anyway.
Nice to see they are finally trying to fix the blatant security flaws in UAC.