I will, if you can unlock Bell Canada. Or Canada Bell. hehe.

I was thinking of starting a thread to ask... who's the sucker who sold for $105? Come on, admit it!! 

50%+ is not a "minor correction", just for your future reference...

The VPS is running OpenVPN and on the 10Mbit/s line, correct? You should be able to. The authentication shouldn't matter at all. No reason to try to authenticate unless the authentication process is so slow it's more efficient to make the server come to a crawl by sending it real authentication requests. You don't have to send it to the particular port. Any traffic, TCP/UDP, to any port, sent to that IP *should* make it there.

That's right, a DDoS could be this many times over from multiple machines. You may be able to find an account on a seedbox or another VPS or two to send the attack. I'd give hping3 a try disabling wait times between packets and with 1500 byte (total) packets. UDP, TCP, shouldn't matter. Note that sending an attack from the box may render the attacker unreachable. A script which kills itself after 10 seconds might be good to get back into it, in case that happens.

Sincerely,
Teran

I'd hold off, this is the one I think.
It will go below $190.

This is coming from a pretty strong bull. It got overextended.

These are good questions and you asked them humbly. I hope this is a good response.


Yes, absolutely. So I'll start with the literal meanings and go into the technicalities.

DoS = Denial of Service
DDoS = Distributed Denial of Service

So a DoS usually comes from one source, or is really small. DDoS is likely to come from a botnet and be rather large, at least in term usage.

A DoS attack can be very simple, or more complicated. If you want to "deny service" from a service, you usually have to keep it from giving service. That could mean simply disconnecting a cable. Or making so many fake orders on a website that there's nothing else in stock, in which case there's no more service which people can take.

More commonly, a DoS can be a network flood enough to saturate the link. If their connection can only handle 10MB/s of traffic and you flood them with 10+MB/s of traffic, not much else is going to get through. Any services, OpenVPN, SMTP/email, HTTP, all depend on the network link on the server to serve traffic. The firewall on the server itself pretty much can do nothing other than drop traffic for ports already open (or move traffic around in silly ways if needed). But it won't stop traffic from hitting the interface. You can send UDP traffic or even a completely different layer 4 altogether, and it'll probably get to the host and have an effect, at least in terms of network saturation.

More efficiently in terms of bandwidth, you can do HTTP benchmarks. If the webserver/web code is slow or particularly misconfigured, that alone will make a website mostly unavailable. If the service is over TCP at all (I think OpenVPN can do TCP and/or UDP), a TCP syn flood is possible.

So you really have to look at network saturation, application saturation, service saturation, and server saturation. If any of those are "saturated", it can  be a successful denial of service.


Kind of iffy. You may have issues with hosting providers on both ends. Most hosting providers don't like their network being needlessly flooded. For a DoS from a single source (or multiple, if you have several VPSs), you can try hping3. I have seen one DDoS-as-a-service website, and maybe there are some "legitimate" ones, but that is still questionable. You can search for them and try them if you like. Your best option is to test it out locally. If you can get three machines and a switch, you can set the server to negotiate to 10Mbit/s (to make it easier) on the ethernet link, have the attacking machine flood the server, and see what happens when the real client tries to reach it.

You can also do that in a VM environment, all on your desktop. Of course, it's not entirely as realistic due to certain factors, but may be enough of a test. And keep in mind, DoS on a switch is much harder than over a router. Routers are so much slower than switches in terms of packet-per-second performance. They are often the bottle neck in many cases.

If you want a good DDoS service to do a real world test (which is a bad idea), you can try the black market sites on Tor.

I hope this helps a bit! Let me know if you have any more questions about this.

Sincerely,
Teran

I have a feeling it will be broken again in the near future, and then not long after that, and then not long after that, repeat for a little while.

Thank you. Did you ever try?

I think people would definitely be interested in a service like that, but make sure it doesn't already exist. I know that the iPhone app btcReport supports price alerts by iOS notifications. If such an SMS service doesn't exist I'd say go for it. You may like to even include a service to automatically cash out their MtGox bitcoins, they would need to be happy giving you their API key however. You would need to access MtGox's API to implement this.

YES

IT IS LAGGING

Lag is :0.12 seconds

If one was forced to make and fpga miner. Is there a reputable source/tutorial to put one together?

...I think when it comes to speculation Gavin and Evoorhees should stay quite and keep to themselves....