commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
It is safe when there is
"PermitEmptyPasswords no"
in /etc/ssh/sshd_config.
This command is useful when there is no need to have a password.
There are 2 alternatives - vote for the best!
-d, --delete
Delete a user?s password (make it empty). This is a quick way to disable a password for an account. It will set the named account passwordless.
If you can do better, submit your command here.
You must be signed in to comment.
you mean "it works when", not "it is safe". someone please explain when it is useful to not have a password on an account?
When you have a computer at home and everybody can use the same account, so it's useful. Since it's empty, one can not login via ssh.
passwd -d $USERis kind of locking a account, not passwordless login on local computer.
Voted down because anything that circumvents or disables security features, specially in this day and age, is not only a bad idea, it's malpractice.