Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I get this when trying to run this command: desktop:~$ grep nobody /etc/passwd
nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
this "nobody" just popped up one day under my normal profile name and i cannot set it to /dev/null. I get permission denied.
You are seeing this error because you don't have permission to edit the /etc/passwd file. Try changing to the root account or invoke an editor using sudo.
BUT ... the nobody account is useful. It is a standard account used to perform tasks that don't require any privileges or normal user account status. The updatedb utility is usually run in a cron job under the nobody account. That way it does not update the locate database with user files unless the "others" group can see those files.
i was told that With a shell of /dev/null, an attacker could not be certain whether the attempted user exists on the system -- not the case where /bin/false or /bin/nologin is the shell.
so i enter; su
then root passwd;
then; chsh /dev/null nobody
i get; Usage: chsh [options] [LOGIN]
Options:
-h, --help display this help message and exit
-s, --shell SHELL new login shell for the user account
to set nobody now to /dev/null do need to just enter; chsh /dev/null nobody -s?
also, are there any potential problems in doing so? sorry but i am VERY new to this.
that did it! you guys are awesome. Since I have used MS systems for so long and support them professionally I am very unfamiliar with Linux in every aspect ( although i do have to say even being as new to it as i am, i am WAY happier to use it than any MS product i have ever seen). I am a pretty big security guy so if anyone could point me to some references on tools to be used in securing my Linux box i would appreciate it. Also, guarddog vs. firestarter, any opinions?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.