SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I think it works like this: first create a new user like you usually do, then run
passwd -d username
as root. The -d switch means "delete", and should remove the password from the given user account, so after that -- if I'm not mistaken -- you could login by just giving your username and not be prompted for a password.
EDIT: of course you should never just run some passwd commands other people tell you to run it's like giving out your bank card PIN to the first fellow asking..instead you could read
and see what the switches do. It sure is insecure not having a password on an account, but if you insist on it..well, it's your choice.
I set my son's password to nothing so all he has to do is press enter after he puts his name in the user space at the KDM screen. All I had to do to do this was press enter without entering a character in the password portion of the kuser utility.
Well it's not that much of a security risk if:
-You unplug that computer,
-wrap a chain around the computer,
-pour cement over that computer.
The most secure system in the world regardless of passwords.
No serius, if you don't have a password than at least make sure not daemons are running, like sshd etc. Then you should be ok, or at least not let your firewall forward ports to these daemons from the outside world. I did this the same for my brother in a hurry and noticing that nothing have happened(yet) I did not yet set his password and configured an autologin(no time).
As mentioned earlier, an autologin setup is probably better than setting a blank password. Having the system autologin only really makes it a local security threat, whereas having no password whatsoever makes it a global, internet-ready security threat.
Well, a global, internet-ready security threat running (a Slack-derived distro of) linux, which is better than other options. Still, for peace of mind, I too would suggest the autologin feature of kdm/gdm. I set my computer to autologin everytime I'm going to be gone for the weekend or something, so that my girlfriend (who is brilliant, but not tech-savvy) can shutdown and startup or, more likely, recover from a power failure. She always has access to the computer, and some degree of security is there.
I haven't played with zenwalk in a while, but it does use gdm last I knew, and doesn't by default run too terribly many daemons that would be a security risk; I think sshd might be a default, as is inetd, so the risk is there without a password. Just a word to the wise.
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
I set my computer to autologin everytime I'm going to be gone for the weekend or something, so that my girlfriend (who is brilliant, but not tech-savvy) can shutdown and startup or, more likely, recover from a power failure. She always has access to the computer, and some degree of security is there.