Do you develop on GitHub? You can keep using GitHub but automatically sync your GitHub releases to SourceForge quickly and easily with this tool so your projects have a backup location, and get your project in front of SourceForge's nearly 20 million monthly users. It takes less than a minute. Get new users downloading your project releases today!
Keep DST, but remove the mandatory biannual whining. Seriously, year round, nobody cares, but twice a year without fail, people bitch about it, and then forget it.
On Windows, you can switch caps lock and ctrl with a registry hack. I always set it up like that to help combat RSI. You most probably the same on Linux, but I don't use Linux enough to know how.
That only works for next-door neighbours - not people across the street or on the other side of a river. And if your next-door neighbour doesn't get it, but the d00d one house further does, you need some way to connect around your neighbour's house. Etc, etc.
It's not just xkcd. When there was a post about Megatokyo's VN,/.'s thread was just a bunch of people whining that it wasn't a gag joke comic any more, even though it hasn't been that since 2002. I'd guess/. is just filled with bittervets?
Same here, we got a call from the hosting company just last week about a huge bandwidth use. Luckily I heard about these style attacks before, so once I noticed them I knew how to stop them. Somewhere out there is a DDoS now with 20 MB/s less. Just our $0.02 I guess.
Posted
by
Unknown Lamer
from the check-your-sources dept.
msm1267 writes with an excerpt From Threat Post: "While the big traffic numbers and the spat between Spamhaus and illicit webhost Cyberbunker are grabbing big headlines, the underlying and percolating issue at play here has to do with the open DNS resolvers being used to DDoS the spam-fighters from Switzerland. Open resolvers do not authenticate a packet-sender's IP address before a DNS reply is sent back. Therefore, an attacker that is able to spoof a victim's IP address can have a DNS request bombard the victim with a 100-to-1 ratio of traffic coming back to them versus what was requested. DNS amplification attacks such as these have been used lately by hacktivists, extortionists and blacklisted webhosts to great success."
Running an open DNS resolver isn't itself always a problem, but it looks like people are enabling neither source address verification nor rate limiting.