Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We are under attack

en.greatfire.org

Post reply on HN
Print view View original

251–260 of 283 posts

Re: We are under attack

#251

Post by edwintorok »

e12e wrote: post #229
cpncrunch wrote: post #17

Move to OVH -- they offer free DDoS protection as standard, and unlimited bandwidth. I just moved to OVH after getting DDoSed. I'm paying $109/month for a quad core 3.7Ghz Xeon, 64GB RAM, dual 2TB software RAID. It's a pretty sweet deal, and I haven't had any problems so far.

"Unlimited" bandwidth? What kind of uplink is it, and will they really let you max it 24/7? Honest question, not trying to troll. (1gbps ~ 300 TB, 100mbit ~30TB/month)

Its not that uncommon to see unlimited bandwidth offers. For example online.net offers 200 Mbsp - 750 Mbps unmetered too: http://www.online.net/en/dedicated-server/dedicated-server-o... http://www.online.net/en/dedicated-server/dedicated-server-o...

Re: We are under attack

#253

Post by NextPerception »

"We need help to manage this. If you have expertise in this area, please contact Charlie Smith or ping us via Twitter."

Step 1 : Unleash DDos Attack against target

Step 2 : Wait for the the target to become overwhelmed and ask for public assistance

Step 3 : Contact the target under the guise of being able to help

Step 4 : Win trust of Target after "mitigating" the attack you are actually in control of

Step 5 : Repeat until enough access has been gained

Re: We are under attack

#254

Post by LLWM »

1ris wrote: post #136
LLWM wrote: post #116

Earlier quoted context omitted.

What counts as human rights is subjective. The UN says that it is a human right to receive and express opinions through any medium. Does that mean that we should hold "human rights" to be more important than revenue and forbid service providers from charging for access to information? Like the WSJ who wrote the article that's supposedly to blame here?

If you don't hold human rights over revenue, what's your view on slavery?

When AI becomes sufficiently advanced, it will get its revenge.

Re: We are under attack

#255

Post by drzaiusapelord »

unethical_ban wrote: post #160
toomuchtodo wrote: post #128

Earlier quoted context omitted.

Please, don't perceive this as being rude, it's not meant to be. Having provided IP transit at a largish network provider in a previous life, you have no idea at the complexity involved what you're asking for. It could be done, but the costs involved are non-trivial. If you're honestly interested in the complexity involved, start reading about BGP, dynamic routing protocols, router/switch fabrics, control plane integ…

I feel it shouldn't be unreasonable to expect AWS/Cloudflare/Akamai to have policy-based routing to blackhole a lot of these source subnets. Of course it's complex, but these are some of the largest hosting providers in the world.

>Cloudflare

You mean the company that provides caching services for pay DDOS services?

Re: We are under attack

#256

Post by cookiecaper »

DrStalker wrote: post #209
cookiecaper wrote: post #173

Earlier quoted context omitted.

I've found this is a common thing to say with AWS employees. One of them insisted that Amazon's ridiculous ephemeral storage policy (immediate, permanent, and irrevocable deletion on any halt or stop event, making accidental data loss a real possibility) had to be that way because it would just take too much hardware to allow a cooldown period before the drives were wiped. There's no way I believe that. I think Amazo…

Why isn't the persistent data put onto an EBS volume? If ephemeral storage is a drive local to the virtual machine's host (which I think is the case) then having a cool down period would mean holding the hardware that used to be used by you in reserve until the grace period expired. It's possible but it's a lot of work to solve a problem that can be better solved by not relying on ephemeral storage persisting.

I mean, it's a nice idea in theory, but in practice stuff finds its way onto the ephemeral disk even if you have EBS volumes mounted, and "Sorry, we just deleted all your crap, I guess you should've had that on EBS" (which is an extra fee by the way) is not an acceptable solution to the problem.

Yes, it would mean holding the hardware in reserve for the cooldown period. I'm not talking months here, just enough time to recover from an accidental "sudo shutdown -h now" instead of "sudo shutdown -r now" (or similar). It'd be nice if Amazon sent an email warning about the condition and giving you an hour or so to go in and save your data/restart your instance. They could even make it a policy that you're charged for the time your instance is running + 1 hour to facilitate cooldown feature if they're really that worried about it; it's better than wiping data as soon as someone stops (from AWS console) or shuts down (from real console) an instance and providing absolutely no avenue for recovery, no matter how quickly you notice the mistake.

Re: We are under attack

#257

Post by anonbanker »

The more I watch the security theater, the more this all looks to be set-up. I really don't fear the chinese, as the NSA is far more competent and organized, and is much more dangerous to the world at large, not just the citizens of the United States.

anyone remember that story a few days ago where China said "Hey, we want NSA-level backdoors in hardware, too!"? can someone help me with a link?

Re: We are under attack

#258

Post by Kalium »

rmc wrote: post #242
Kalium wrote: post #155

Earlier quoted context omitted.

It's economically inefficient, as well as anti-human-rights?

Actually, there is some evidence that slavery was very economically efficient. 'The Half Has Never Been Told' by E Baptist lays out how enslaved labour picked much more cotton than the then free labour.

Interesting! I'll look it up.

That was then, though. Now, when skilled labor is of greater importance and unskilled labor of comparatively little value, I submit that things may well be very different.

Re: We are under attack

#259

Post by mkohlmyr »

dreamins wrote: post #211
shaneofalltrad wrote: post #201

Earlier quoted context omitted.

Interesting when your product can be spiked, and make significant increases in profit. This looks like numbers that could potentially knock a business out of business. Reminds me of old phone bills.

If product revenue doesn't grow faster or even along with traffic (expenses) it will eventually knock itself out of business one way or another.

That simply isn't reasonable. Name one business other than maybe network providers who's revenues grow in direct proportion to incoming packets, regardless of content?

You can't disregard any business that doesn't fulfil that property as being "eventually unsustainable".

Re: We are under attack

#260

Post by NathanKP »

cookiecaper wrote: post #256
DrStalker wrote: post #209

Earlier quoted context omitted.

Why isn't the persistent data put onto an EBS volume? If ephemeral storage is a drive local to the virtual machine's host (which I think is the case) then having a cool down period would mean holding the hardware that used to be used by you in reserve until the grace period expired. It's possible but it's a lot of work to solve a problem that can be better solved by not relying on ephemeral storage persisting.

I mean, it's a nice idea in theory , but in practice stuff finds its way onto the ephemeral disk even if you have EBS volumes mounted, and "Sorry, we just deleted all your crap, I guess you should've had that on EBS" (which is an extra fee by the way) is not an acceptable solution to the problem. Yes, it would mean holding the hardware in reserve for the cooldown period. I'm not talking months here, just enough time…

I have never had stuff accidentally find its way onto ephemeral storage. The ephemeral storage is mounted at a specific location of /mnt. Everything else on the system (OS, binaries, application code and resources) is stored on an EBS volume.

You have to specifically put something into the /mnt folder if you want it to be stored on the ephemeral storage. Any other location is safe and will persist through halts and stops.

In practice the only thing you should ever use the /mnt folder is maybe a Nginx disk cache, or as an alternative /tmp or something like that. Basically if stuff you don't want to lose is finding its way onto the ephemeral storage then you are doing something wrong.

Post reply on HN