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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



Find brute force attempts on SSHd

Terminal - Find brute force attempts on SSHd
cat /var/log/secure | grep sshd | grep Failed | sed 's/invalid//' | sed 's/user//' | awk '{print $11}' | sort | uniq -c | sort -n
2009-03-30 15:48:24
User: empulse
Functions: awk cat grep sed sort sshd uniq
Find brute force attempts on SSHd

Searches the /var/log/secure log file for Failed and/or invalid user log in attempts.


There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

On Ubuntu, it's /var/log/auth.log

Comment by goodevilgenius 317 weeks ago

cat overload! :-)

< /var.log/secure grep sshd | grep Failed | sed 's/invalid//' | sed 's/user//' | awk '{print $11}' | sort | uniq -c | sort -n

Comment by mpb 317 weeks ago

I was wondering why have the sed commands? Wouldn't just making awk '{print $13}' make more sense? I'm a bash newbie and would love the explanation.

Comment by frailotis 317 weeks ago

After messing around, here's what I've got and I think it's a bit cleaner. Let me know if that's true or not.

awk '/sshd/&& /Failed/ {print $13}' /var/log/secure | uniq -c | sort -nr

Comment by frailotis 317 weeks ago

@frailotis you need to sort first before piping to uniq, Also, you're missing some IP addreses and getting random data by not searching and replacing for "invalid user". However, yes, people need to learn awk rather that pipe cat to grep to grep to sed to sed then to awk, with sort used twice!

awk '/sshd/ && /Failed/ {sub(/invalid user/,""); print $11}' /var/log/auth.log | sort -n | uniq
Comment by atoponce 316 weeks and 6 days ago

BTW- /var/log/secure on Fedora-based systems, /var/log/auth.log in Debian-based systems.

Comment by atoponce 316 weeks and 6 days ago

You can make the original command a little cleaner by combining sed expressions like this:

cat /var/log/messages | grep sshd | grep Failed | sed -e 's/invalid// ; s/user//' | awk '{print $11}' | sort | uniq -c | sort -n
Comment by unixmonkey6951 284 weeks and 6 days ago

Your point of view

You must be signed in to comment.