this post was submitted on 11 Nov 2024
-36 points (21.9% liked)
Linuxsucks
206 readers
31 users here now
Rules:
- FOSS advocates and Linux evangelists aren't welcome. -We ask that you block us.
- Moderation is heavy handed. Try to stay on topic.
- No Complaining Mute the sub if users, content, or rules bother you
founded 2 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Correct. But the thing configured there is "to act on behalf of root for these items", not the "things" themselves.
It is not you executing stuff with
sudo
.file1
is owned by you, butfile2
is owned byroot
.There is a point. See above.
That's not an argument I've made, nor make.
Both of which are much easier to defeat than a pop up confirmation dialog with a text box for your password.
No it doesn't - you seem to be making things up to justify your lack of understanding. Authentication is not the same as authorisation, nor should it be treated the same way.
When you type in your password on a login prompt - you authenticate who you are.
When you type in your password on a sudo prompt - you authorise a command to be carried out on behalf of
root
.I'm not sure you realise how little you do on a windows machine. Good luck installing system software or altering system files on an AD managed Windows machine without authorisation. Which is what your meme(?) is implying.
There is no justification here, just a manufactured statement.
See above.