uncleflo
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 1 bookmarks
howto information development guide reference administration design website software solution service online product business uk tool company linux code server application system web list video marine create data experience tutorial description learn explanation technology build article blog world boat project download windows lookup security free performance javascript technical london control network beautiful tools support course file research purchase image library programming youtube example php opensource install construction community html quality feature profile computer power browser music platform mobile process work manage professional user share database hardware buy industry internet dance advice developer installation search 3d camera access customer travel material standard money test develop css review documentation engineering photography webdesign engine digital device speed api source event question program management client phone discussion story water simple content marketing app yacht account setup idea interface package fast communication cheap compare script market study easy live google resource operation demonstration contact startup
Tag selected: privileged.
Looking up privileged tag. Showing 1 results. Clear
users - How do daemons work? - Unix & Linux Stack Exchange
Saved by uncleflo on January 4th, 2019.
If a user wants to execute a command, he has to first log in into a system. But some users in the system have /bin/false or /sbin/nologin set as a default shell in the /etc/password file. If I change /bin/bash to /bin/false in case of my user, I won't be able to log in into the system, so I also won't be able to run commands. But the shellless users do it anyway: How can a user without a shell execute a command? In POSIX, every running process has three User IDs (UIDs) associated with it; the real UID, which identifies the user who launched the process, the effective UID, which is used to determine what resources the process can access, and the saved Set-User-ID (SUID), which is the effective UID the process had when it started (at the point of the last exec() call). Of these, the effective UID is the most significant, since it is the one used when determining access control decisions regarding the process.
privileged unix unprivileged stack bash answers acknowledge user execute privilege answer effective privacy processes default exchange daemon administration developer development code server linux
No further bookmarks found.