denial-of-service

Can't Access Plesk Admin Because Of DOS Attack, Block IP Address Through SSH?

江枫思渺然 提交于 2019-12-05 08:25:50
I can't access Plesk Amdin because of DOS attack; can I block a hostname or IP address through SSH? If so, how would I be able to do this? Thank you! If you have iptables you can block it using simple rule: iptables -I INPUT --source 1.2.3.4 -j DROP This rule drops packets coming from IP 1.2.3.4. Probably the easiest is to SSH to your box use vim to and add the following to the top of your .htaccess file in the root of your domain ( /var/www/vhosts/yourdomain.com/httpdocs/.htaccess ): deny from 12.345.67.89 Obviously replace the IP address with the one you want to block. Repeat this for any

Does Windows Azure have anything readily available against denial of service attacks?

主宰稳场 提交于 2019-12-04 20:13:05
问题 We're developing a web service hosted in Windows Azure. We expect that at some moments bad guys try to DDOS it. I Googled and didn't find anything new and definitive (this one is rather vague) about whether Windows Azure has some features against denial of service attacks. Do we need any special measures? What does Windows Azure offer to protect against denial of service attacks? 回答1: The Azure load balancer provides some protection, but the details of this are not published. 回答2: I reckon no

Servlet filters for abuse prevention? (DoS, spam, etc)

﹥>﹥吖頭↗ 提交于 2019-12-04 09:52:48
I'm looking for a servlet filter library that helps me secure our web service against unauthorized usage and DDoS. We have "authorized clients" for our web service, so ideally the filter would help detect clients that aren't authorized or behave improperly, or detect multiple people using the same account. Also we need a way to prevent DoS'ing of our various services since we have an open-account policy -- limiting the number of simultaneous connections for a user, etc. We've looked at the Tomcat LockOutFilter and such but those are fairly primitive and only prevent against one sort of attack.

PHP: Opening URLs concurrently to simulate a DOS attack?

倾然丶 夕夏残阳落幕 提交于 2019-12-03 15:06:22
问题 I have configured my server with various anti-DOS modules (mod_qos, mod_evasive etc). What I want to do now is run a simple PHP scrip that calls URLs on my site multiple times, in order to reach the various limits on the site. Ideally a script that can somehow open various URLs concurrently would be ideal. Is this possible? And if not, what is the easiest way to simulate multiple requests from one IP? I would prefer a tool that works in Windows 7? Update: Remember, i want to be able to see if

PHP: Opening URLs concurrently to simulate a DOS attack?

こ雲淡風輕ζ 提交于 2019-12-03 03:58:57
I have configured my server with various anti-DOS modules (mod_qos, mod_evasive etc). What I want to do now is run a simple PHP scrip that calls URLs on my site multiple times, in order to reach the various limits on the site. Ideally a script that can somehow open various URLs concurrently would be ideal. Is this possible? And if not, what is the easiest way to simulate multiple requests from one IP? I would prefer a tool that works in Windows 7? Update: Remember, i want to be able to see if my server is actually blocking some of the requests. I've only played with AB for a little bit, but so

What is the best way to protect against DDOS attacks? [closed]

♀尐吖头ヾ 提交于 2019-12-02 18:21:14
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 3 years ago . I live in an open community.. I run a game on a dedicated server and have no idea about ddos security, I am trying to stop concurrent attacks against my game server but have no idea where to make my first movie, its like I am checkmated in an intense game of chess, do I use another hosts protection? do I build

Denial of Service attack on Parse.com app

戏子无情 提交于 2019-11-30 12:09:38
I'm writing a small web application as I'm learning to use the features of Parse.com. Since application_id and javascript_key are both public (as explained in the doc), it means anyone is free to run code like illustrated in the following snippet: function sendRequest(){ var query = new Parse.Query(Parse.User); query.find({ success: function(results) { console.log("Request sucessful"); }, error: function(error) { console.log("Request error: " + error.code + " " + error.message); } }); } setInterval(sendRequest, (1000 / hitsPerSecond)); I think it can lead to "DOS" attacks pretty easily -

Which kind of webapps can realistically be affected by the floating bug?

≡放荡痞女 提交于 2019-11-30 07:09:45
There's an easy way to totally lock a lot of JVM: class runhang { public static void main(String[] args) { System.out.println("Test:"); double d = Double.parseDouble("2.2250738585072012e-308"); System.out.println("Value: " + d); } } or, to hang the compiler: class compilehang { public static void main(String[] args) { double d = 2.2250738585072012e-308; System.out.println("Value: " + d); } } as explained here: http://www.exploringbinary.com/java-hangs-when-converting-2-2250738585072012e-308/ My question is very simple: which kind of well-conceived web application do you know that can

Best practices for detecting DOS (denial of service) attacks? [closed]

放肆的年华 提交于 2019-11-30 01:53:56
I am looking for best practices for detecting and preventing DOS in the service implementation (not external network monitoring). The service handles queries for user, group and attribute information. What is your favorite source of information on dealing with DOS? This is a technique I found very useful.. Prevent Denial of Service (DOS) attacks in your web application Whatever you do against DoS-Attacks, think if what you do may actually increase the the load required to handle malicious or unwanted requests! If you are using Linux then you should read this article: Rule-based DoS attacks

Denial of Service attack on Parse.com app

孤人 提交于 2019-11-29 17:59:46
问题 I'm writing a small web application as I'm learning to use the features of Parse.com. Since application_id and javascript_key are both public (as explained in the doc), it means anyone is free to run code like illustrated in the following snippet: function sendRequest(){ var query = new Parse.Query(Parse.User); query.find({ success: function(results) { console.log("Request sucessful"); }, error: function(error) { console.log("Request error: " + error.code + " " + error.message); } }); }