Timeline for SETUID and SETGID Behavior
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2017 at 9:13 | comment | added | Devidas | Hey Ben, It may be due to different group ids (ht and sudoers have same uid and gid but not ht and shadow ) I am just helping explaining behavior. because even this is true still weird. | |
| Sep 12, 2017 at 7:05 | comment | added | Kusalananda♦ | What error do you get from ht when you try? Please update the question with the exact and full error message that you get. | |
| Sep 12, 2017 at 4:20 | comment | added | rootshellz | Interesting. Maybe it is the ht application then. ht is an ncurses hex editor. | |
| Sep 12, 2017 at 4:16 | comment | added | muru | I have not idea what ht is, but I tried the same setgid/setuid permissions on copies of cat and vim and both programs were able to read both files perfectly fine. (Vim complained about /etc/sudoers being read-only, of course.) On Ubuntu 16.04 | |
| Sep 12, 2017 at 2:49 | review | First posts | |||
| Sep 12, 2017 at 4:11 | |||||
| Sep 12, 2017 at 2:44 | history | asked | rootshellz | CC BY-SA 3.0 |