What's this?

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.

Get involved!

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.

Universal configuration monitoring and system of record for IT.

Stay in the loop…

Follow the Tweets.

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

Subscribe to the feeds.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Harder, Faster, Stronger SSH clients

Terminal - Harder, Faster, Stronger SSH clients
ssh -4 -C -c blowfish-cbc
2009-12-15 00:30:53
User: vxbinaca
Functions: ssh
Harder, Faster, Stronger SSH clients

We force IPv4, compress the stream, specify the cypher stream to be Blowfish. I suppose you could use aes256-ctr as well for cypher spec. I'm of course leaving out things like master control sessions and such as that may not be available on your shell although that would speed things up as well.


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

You are right in using "Harder" since this command is harder to type than "ssh". :-) To speed test other ciphers, the openssl command provides a speed test which you can run on your own machine:

openssl speed aes rc4 blowfish
Comment by bwoodacre 388 weeks and 4 days ago

@bwoodacre Thats why you alias it in your .bashrc. External programs who call it won't be calling the alias.

Comment by vxbinaca 388 weeks and 4 days ago

Or put this in ~/.ssh/config to do the same thing in a more readable way and avoid the alias:

Host *

AddressFamily inet

Compression yes

Cipher blowfish

Comment by bradleybuda 388 weeks and 3 days ago

Forcing ipv4 seems a bit pointless & short-sighted. I for one use IPv6 almost exclusively on my LAN.

Comment by snow93 387 weeks and 6 days ago

The rest of the world unfortunately uses 4, but 6 can be forced as well. You use it for domains, ex:

[alias'd SSH] srv1.domain.com -p 3345
Comment by vxbinaca 387 weeks and 6 days ago

Your point of view

You must be signed in to comment.