3 ms·
There are multiple ways to set things up in Linux. You can use sudo, or you can have a separate root user. I have not used Windows enough in recent years to kn
by graemep 2y ago
There are multiple ways to set things up in Linux. You can use sudo, or you can have a separate root user.
I have not used Windows enough in recent years to know, but there may be differences in what you need to enter your admin password for, which may make users less suspicious when asked. On Linux distros I have used the only regular operation on a desktop that requires it are software installation and updates updates, which has a well defined UI and comes after a specific user action.
- gruez 2y ago>but there may be differences in what you need to enter your admin password for, which may make users less suspicious when asked. On Linux distros I have used the only regular operation on a desktop that requires it are software installation and updates updates, which has a well defined UI and comes after a specific user action. clearly you haven't seen all the projects on github where the instructions are "curl ... | sudo sh". Moreover, the security model behind sudo is so hilariously bad that it's trivial to get EoP[1]. UAC might have plenty of exploits (usually around auto-escalation), but at least they make an attempt at making it secure. [1] tl;dr: modify $PATH to contain a bobbytrapped version of sudo that executes the command you want, plus whatever evil stuff you want.
- mycall 2y agoReserve shells are indeed simple in *nix
- graemep 2y ago> learly you haven't seen all the projects on github where the instructions are "curl ... | sudo sh". I have seen them. I do not use them! I very rarely install anything from outside distro repos or language repos. > Moreover, the security model behind sudo is so hilariously bad that it's trivial to get EoP[1]. UAC might have plenty of exploits (usually around auto-escalation), but at least they make an attempt at making it secure. You have missed my point. You do not have to use sudo