You must be new here. Every patent story on Slashdot is like this, and in every case theres tons of people jumping in who can't seem to understand the abstract is just that.. an abstract. You need to read the actual claims and description to see what is being patented.
But lets not get into way of some good sensationalism journalism.
How do you know that one of them isn't proper and the rest are merely deviations from proper? Or, more accurately, how do you know what it is supposed to look like if you say they are all wrong?
However, my question for you is whether or not anything is accomplished by blocking these addresses.
After blocking a bulk of them at the firewall level, doing a "iptables -nL -v |less" shows (first column) a bit of them still throwing packets at the machine, and some of them just keep trying even after they've been blocked for more than a day (perhaps longer even). So, at least in my opinion, it does accomplish something for me at least, knowing that the sshd daemon isn't being bothered as much, and my logcheck mails are smaller.
It appears to be coordinated. One IP will hit once or twice the move on, then a minute or two later another IP will try once or twice. We're running fail2ban to block out the bulk attempts, but all I'm doing for the one-shot'ers is just collecting the unique address then blocking them with iptables. Not much more I can do without making it a research project.
Same here, for some reason one of our servers on our subnet is a frequent attack for distributed SSH attacks, and there has been an explosion of them in the past few days for us. I've been collecting IP addresses and locking them out via firewall, but more just keep coming.
Slashdot Mirror
It also says:
The link is at least more likely than to Leonardo da Gary Indiana.
You must be new here. Every patent story on Slashdot is like this, and in every case theres tons of people jumping in who can't seem to understand the abstract is just that.. an abstract. You need to read the actual claims and description to see what is being patented.
But lets not get into way of some good sensationalism journalism.
"journalism"? Are YOU new here? :)
A lot of mindshare and goodwill, centering on the Ruby on Rails framework.
Nothing against Rails, but there's a lot more to Ruby and the Ruby community than that one web framework.
It was a joke.
they day they dropped MST3K. Bastards...
the users...
Be sure and leave a comment on Stephen King's page. Truly an American icon.
"Slashdot? Pfft. It'll never last."
Slashdot of yore didn't last. Slashdot of mindless fanboyism killed it. Now with 30495% more JavaScript as well!
Thong... the fish is ready.
Springs and the support post are under the seat? Call me old fashioned (and it won't be the first time) but I'll take a horse, thank you.
NO SPRINGS!
I'm Dialing Lucky
As a guy who reads, trusts and respects slashdot and the community here
You lost me.
idk my BFFFFFFF jill?
How do you know that one of them isn't proper and the rest are merely deviations from proper? Or, more accurately, how do you know what it is supposed to look like if you say they are all wrong?
It's Slashdot, incompetence is assumed.
As long as it doesn't cause Lupus...
+1. Taco must be fishing for clicks to post this tripe outside of the already worthless "Politics" section.
base-9 or base-11?
NEVER FORGET
"[The iPod has] No wireless. Less space than a nomad. Lame."
So naturally samzenpus decides to talk about him. Brilliant.
I haven't seen the addresses come back later
Some of them do keep trying from what I've seen.
However, my question for you is whether or not anything is accomplished by blocking these addresses.
After blocking a bulk of them at the firewall level, doing a "iptables -nL -v |less" shows (first column) a bit of them still throwing packets at the machine, and some of them just keep trying even after they've been blocked for more than a day (perhaps longer even). So, at least in my opinion, it does accomplish something for me at least, knowing that the sshd daemon isn't being bothered as much, and my logcheck mails are smaller.
It appears to be coordinated. One IP will hit once or twice the move on, then a minute or two later another IP will try once or twice. We're running fail2ban to block out the bulk attempts, but all I'm doing for the one-shot'ers is just collecting the unique address then blocking them with iptables. Not much more I can do without making it a research project.
Same here, for some reason one of our servers on our subnet is a frequent attack for distributed SSH attacks, and there has been an explosion of them in the past few days for us. I've been collecting IP addresses and locking them out via firewall, but more just keep coming.
to "faildawson" (amirite?)
If I want actual Intellectual articles with in-depth discussions, I come to slashdot.
Gold, Jerry! Gold! /been here since before user accounts