Timeline for How are setuid, suid, sudo, and su all related?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 14, 2018 at 16:47 | history | suggested | Miles | CC BY-SA 4.0 |
gender nit
|
| Nov 14, 2018 at 13:35 | review | Suggested edits | |||
| S Nov 14, 2018 at 16:47 | |||||
| Jan 26, 2016 at 11:56 | comment | added | jcbermu | it's important because it can be assigned only to specific executables. | |
| Jan 26, 2016 at 11:55 | comment | added | jcbermu |
If you issue a ls -l /usr/bin/passwd the result will show an s in the executable bit of the owner. That is the setuid bit
|
|
| Jan 26, 2016 at 11:42 | comment | added | Melab |
So why have setuid bits if you have sudo or su? And if setuid bits are so important, then why don't see I see any of them when I use ls on important system executables?
|
|
| Jan 26, 2016 at 9:29 | history | edited | jcbermu | CC BY-SA 3.0 |
added 27 characters in body
|
| Jan 26, 2016 at 9:28 | comment | added | jcbermu | Yes. It's true. I'll change my answer. | |
| Jan 26, 2016 at 9:27 | comment | added | Hauke Laging | "become another user" meaning "run a (new) shell / program as another user". It does not change the permissions of running processes. | |
| Jan 26, 2016 at 9:22 | history | answered | jcbermu | CC BY-SA 3.0 |