You can not change my mind.
-
I
AM
ROOT"I am Steve Rogers."
-
Heh, pee sex EC...
EC?
* Ursula von der Leyen enters the chat… -
This post did not contain any content.
sudo echo nah I am root baby. -
EC?
* Ursula von der Leyen enters the chat…FUCK
-
This post did not contain any content.
We've had 24 years of UAC and somehow Microsoft still can't figure out either of the following:
-
The UAC prompt is triggered by an application either directly requesting elevation, or attempting to do something (write a file, tweak a registry value, change a group policy setting) that requires said permissions. So the OS obviously knows whatever it was the application tried to do, but it doesn't tell you what that is. It just says it needs to make "changes to your device." I would feel a lot better about that if they bothered to inform me maybe which file or directory it was trying to write to, or if it's a registry change, or what. Because, you know, maybe I don't want to let randomdownloadedapp32.exe change my system language to Swahili if I knew that's what it was about to do.
-
There still isn't a way to permanently mark a specific app or executable as trusted so it won't nag you about UAC elevation. If you're running an account with limited permissions and need to enter an administrator password every single time you launch some damn fool program, for instance, that's a big time problem for your peons who may accidentally close that application at any time and then can't reopen it. The workarounds for this (if any) typically revolve around divining whatever action that app performs that's got Windows' knickers in a twist, rather akin to guessing what a fussy baby is crying about, and then manually applying permissions to that file, directory, or object. Maybe it's trying to write to %systemdrive%\Program Files? Maybe it's keeping a count of something in the registry? Did it try to change a protected system setting like, ye gods forbid, the clock? Did it trip Windows' built in installer detection? Or maybe it just blithely demands an elevated runtime for no reason because its developers were morons. I don't fucking know, because the UAC prompt doesn't tell you; See point #1 above.
-
-
sudo echo nah I am root baby.This incident will be reported!
-
It's funny that elevation of permissions is something handled elegantly in Linux since forever, but M$ just can't make it happen.
UAC is slow, ineffective, and inconsistent. But even when you turn it off you find some directories are off limits still. Even while you can vandalize regedit and gpedit all day long.
The "hello Windows" system of pins and bio-metrics may be an improvement, IDK. I liked using a PIN for logins and stuff right up until I needed the real password for something.
Or maybe that's the problem: the fact that M$ handles elevation of permission in 6 different and contradictory ways that all have to be backward comparable.
Windows has sudo now.
-
We've had 24 years of UAC and somehow Microsoft still can't figure out either of the following:
-
The UAC prompt is triggered by an application either directly requesting elevation, or attempting to do something (write a file, tweak a registry value, change a group policy setting) that requires said permissions. So the OS obviously knows whatever it was the application tried to do, but it doesn't tell you what that is. It just says it needs to make "changes to your device." I would feel a lot better about that if they bothered to inform me maybe which file or directory it was trying to write to, or if it's a registry change, or what. Because, you know, maybe I don't want to let randomdownloadedapp32.exe change my system language to Swahili if I knew that's what it was about to do.
-
There still isn't a way to permanently mark a specific app or executable as trusted so it won't nag you about UAC elevation. If you're running an account with limited permissions and need to enter an administrator password every single time you launch some damn fool program, for instance, that's a big time problem for your peons who may accidentally close that application at any time and then can't reopen it. The workarounds for this (if any) typically revolve around divining whatever action that app performs that's got Windows' knickers in a twist, rather akin to guessing what a fussy baby is crying about, and then manually applying permissions to that file, directory, or object. Maybe it's trying to write to %systemdrive%\Program Files? Maybe it's keeping a count of something in the registry? Did it try to change a protected system setting like, ye gods forbid, the clock? Did it trip Windows' built in installer detection? Or maybe it just blithely demands an elevated runtime for no reason because its developers were morons. I don't fucking know, because the UAC prompt doesn't tell you; See point #1 above.
it just blithely demands an elevated runtime for no reason because its developers were morons.
It’s always, always, this one.
-
-
Windows has sudo now.
[citation needed].
Just tried it, got told that it is not a valid command.
-
We've had 24 years of UAC and somehow Microsoft still can't figure out either of the following:
-
The UAC prompt is triggered by an application either directly requesting elevation, or attempting to do something (write a file, tweak a registry value, change a group policy setting) that requires said permissions. So the OS obviously knows whatever it was the application tried to do, but it doesn't tell you what that is. It just says it needs to make "changes to your device." I would feel a lot better about that if they bothered to inform me maybe which file or directory it was trying to write to, or if it's a registry change, or what. Because, you know, maybe I don't want to let randomdownloadedapp32.exe change my system language to Swahili if I knew that's what it was about to do.
-
There still isn't a way to permanently mark a specific app or executable as trusted so it won't nag you about UAC elevation. If you're running an account with limited permissions and need to enter an administrator password every single time you launch some damn fool program, for instance, that's a big time problem for your peons who may accidentally close that application at any time and then can't reopen it. The workarounds for this (if any) typically revolve around divining whatever action that app performs that's got Windows' knickers in a twist, rather akin to guessing what a fussy baby is crying about, and then manually applying permissions to that file, directory, or object. Maybe it's trying to write to %systemdrive%\Program Files? Maybe it's keeping a count of something in the registry? Did it try to change a protected system setting like, ye gods forbid, the clock? Did it trip Windows' built in installer detection? Or maybe it just blithely demands an elevated runtime for no reason because its developers were morons. I don't fucking know, because the UAC prompt doesn't tell you; See point #1 above.
What is interesting to me is that Steam somehow manages to run elevated commands when installing games and it, itself, never actually gives any UAC warnings and even kinda breaks if you force Steam to run as an admin from the compatibility tab.
-
-
[citation needed].
Just tried it, got told that it is not a valid command.
Had to enable it, and got prompted to do so, but it works just fine.
-
This post did not contain any content.
MyDarkestTimeline01 is not in the sudoers file. This incident will be reported.
-
MyDarkestTimeline01 is not in the sudoers file. This incident will be reported.
Well didn't know what that was before so, go ahead.
-
This post did not contain any content.
how can you revert 2 million years of evolution in a human in 3.2 seconds with just a simple phrase?
-
It's funny that elevation of permissions is something handled elegantly in Linux since forever, but M$ just can't make it happen.
UAC is slow, ineffective, and inconsistent. But even when you turn it off you find some directories are off limits still. Even while you can vandalize regedit and gpedit all day long.
The "hello Windows" system of pins and bio-metrics may be an improvement, IDK. I liked using a PIN for logins and stuff right up until I needed the real password for something.
Or maybe that's the problem: the fact that M$ handles elevation of permission in 6 different and contradictory ways that all have to be backward comparable.
. . .6 different and contradictory ways that all have to be backward comparable.
After witnessing their handling of Control Panel vs. "trendy no-option we-think-you're-stupid Control Panel" for like 4 straight versions, I think this has just become their philosophy at this point. Lol
-
What is interesting to me is that Steam somehow manages to run elevated commands when installing games and it, itself, never actually gives any UAC warnings and even kinda breaks if you force Steam to run as an admin from the compatibility tab.
Unfortunately, I think the explanation for this one is that Steam bypasses a lot of Windows security and can be used as an exploration vector.
-
This post did not contain any content.
I use to think if I opened Explorer as an administrator I could turn off the parental controls my mom put on the computer
-
This post did not contain any content.
I cannot change your mind -
This post did not contain any content.wrote last edited by [email protected]
Sudo su -
Sudo dnf remove windows
-
it just blithely demands an elevated runtime for no reason because its developers were morons.
It’s always, always, this one.
Moron developer chiming in: it's definitely this.
