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:
You can also use sha1sum and variants for longer passwords
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
1. 32 character length is too long for a password. If you ask md5sum to give you the password every time you need it, the security risk is too high.
2. It only has [0-9a-f], how can you think it is hard to crack?
jxy:
While your first point is valid, your second one is not. A 32-character password using base-16 has: 16^32 password possibilities, which comes out to about 3.4 x 10^38.
Let's say you use lower & uppercase letters, numbers, and a reasonable amount (20) different special characters. A password would have to be length 20 to match that order of magnitude. And 20 characters is also rather long.
jxy: I won't tell you're wrong about asking md5sum every time for a password, but at least is more secure than using "love". Also, since most cracking apps first try using a dictionary attack, this can improve just a little bit your security. I know there are many ways of getting a more secured password, but hey, this is just another way.
Well, you could pipe the output of your command to base64 to get numbers and upper and lower letters. You could also pipe to cut to make it shorter (or just use the first n chars if you're just going to select it with your mouse). You'll also possibly get hyphen and slashes, which you could remove with tr -d if your particular application didn't like those chars. So, for example:
echo "A great password"|md5sum|base64|tr -d /-|cut -c1-12MjgwZTI1YWRl
I just use the pwgen command (pwgen.sf.net).