uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 1 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile work user process database share manage hardware professional buy industry internet dance advice installation developer 3d search access customer travel camera material test standard review documentation css money engineering develop webdesign engine device photography digital api speed source management program phone discussion question event client story simple water marketing app content yacht setup package fast idea interface account communication cheap compare script study market live easy google resource operation startup monitor training
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.