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:
Retrieve top ip threats from http://isc.sans.org/sources.html and add them into iptables output chain.
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
upvoted++
good job. But may I humbly submit that you drop the awk in favor of:
...| perl -pi -e 's/^.*ip=(.*?)".*/\1/;s/^0//' | ...by the way, the perl version I just provided takes care of whacking off the leading zeros that they use to "pad" the IP addresses for easier sorting (quoting the web page). This isn't taken into account in the awk code.
turns out there's a much more easily scraped version provided here: http://isc.sans.org/ipsascii.html
It would also seem that they are padding each octet with leading zeros. In this case ...
curl -s http://isc.sans.org/ipsascii.html|grep -v '#'|awk '{print $1}'|perl -pi -e 's/(?:^0{1,})|(?:(?<=\.)0{1,}(?!\.))//g'Maybe is a good idea to filter the ip addresses which could match with internal ones (today in that list, 10.50.50.50 appeared!)
curl -s http://isc.sans.org/ipsascii.html|grep -v '#'|awk '{print $1}'|perl -pi -e 's/(?:^0{1,})|(?:(?
Sorry:
curl -s http://isc.sans.org/ipsascii.html|grep -v '#'|awk '{print $1}'|perl -pi -e 's/(?:^0{1,})|(?:(?<=\.)0{1,}(?!\.))//g'|egrep -v '^192\.|^10\.|^172\.|^224\.'Great catch, jaguasch
Excellent work guys.
Jaguash, I love your addition, but it will remove non-private IPs. How about this?
curl -s http://isc.sans.org/ipsascii.html | grep -v '#' | awk '{print $1}' | perl -pi -e 's/(?:^0{1,})|(?:(?<=\.)0{1,}(?!\.))//g' | grep -v - P '^10\.|^172\.(16|17|18|19|20|21|22|23|24|25|26|27|28|29|30|31)\.|^192\.168\.'You could also cut the regex down a bit more.
curl -s http://isc.sans.org/ipsascii.html | grep -v '#' | awk '{print $1}' | perl -pi -e 's/(?:^0{1,})|(?:(?<=\.)0{1,}(?!\.))//g' | grep -v -P '^10\.|^172\.((1[6-9])|(2[0-9])|(3[0|1]))\.|^192\.168\.'