News for hackers. Stuff that matters.

rudhir-secpanel

Re:IBM to Acquire SoftLayer on Tuesday June 04, 2013 @01:02PM (#5820652)
Texas has been a magnet for data centers for years.
Re:Why Plivo Cloud is better than Twilio on Tuesday July 31, 2012 @09:21PM (#4320641)
So, does this mean that I can use my existing IP hard phones and control them via plivo cloud?
Yes. When one is logged in as a gmail user, any google search is done as that user. Therefore the requests will carry session information just as if one were using gmail with http.
The google search tab on the right top in Safari/iPad is what a user tends to search in, instead of opening up a new browser tab. This opens up http://google.com, which is the issue.
Re:Secpanel integration with Webmin on Wednesday June 13, 2012 @06:07PM (#4108722)
Re:WHMCS Hacked on Tuesday May 22, 2012 @07:57AM (#4007359)
They claim it was a social engineering attack. Their entire database has been compromised and put on pastebin.

This is just months after the Local file disclosure vulnerability and the remote code injection vulnerability.

Looks like their twitter account has been compromised too. Tweet - "We laugh at your security. #UGNazi"

Re:What should every programmer know about security? on Tuesday May 08, 2012 @06:37AM (#3943024)
http://www.behind-the-enemy-lines.com/2012/04/google-attack-...

Interesting post which showed how badly configured linkages between private google docs and S3 caused an accidental DoS.

Re:What should every programmer know about security? on Monday May 07, 2012 @03:57PM (#3940691)
Backtrack is used to install/host metasploit. If you find Metasploit daunting then you could use Armitage - a gui interface for metasploit.
Thank you for your comments. I am always learning and take this opportunity to do that as well from someone with a better insight and experience.

On the specific points raised here, please go through:

http://lwn.net/Articles/338407/

Given above is also a similar(not the same) kind of attack, which can bring down an apache web server.

Quoting from this link, "It is not entirely clear which web servers have the means to defend against the attack, but there is general agreement that there is no way for Apache to completely defend against it, and that IIS is not vulnerable to the slowloris technique."

Also quoting, "Obviously, this is an application level attack. In their book on Internet Denial of Service, Mirkovic/Dietrich et. al noted that application level DoS is difficult to handle: "[...] many defenses are not able to help you defend against this kind of attack".

So we are back to what the Apache Security team concluded: This is an inherent problem for servers. If you want to serve, then you have to accept clients, and, if they intend to block you, so be it.

But, let's not give up so fast. Obviously, if the well-known proprietary alternative from Microsoft, IIS, is not affected by this problem, there are other solutions. What IIS does differently, is in the way it handles incoming requests: There is no static tie between a worker thread and a network socket in IIS. Rather, the workers are organized in a pool where they wait for incoming TCP packets (rather than TCP connections as Apache does). These packets are then assigned dynamically to threads. So, an idle connection occupies a socket, but it does not block an entire thread. Thus the web need not be shut down by penny-wielding customers or slowloris. "

If all that the attack has to do with is TCP/IP and has nothing to do with the (type of) web server, it should bring down an IIS server as well. No? Then why is that not the case, above?

1. Any denial of service attack will have to be about connections and therefore tcp/ip. Is that what I missed mentioning? But that is not what this is about. 2. Even http also belongs to the family of tcp/ip 2. The point here is that the attack takes advantage of the way apache or nginx treat connections. It is not a simple tcp/ip flooding. 4. What was it, again, that I am marketing, here?

we have been working on this and have had some success in detecting and stopping an attack. would be glad to share more details, if you want
Thanks for you 'vote' :). I have responded to the issue of nginx vs os
the attack was done with slow http traffic. the delay effect on an apache server on the same os(centos) was different than was on nginx(again on centos). also i have been able to control the attack by focusing on the web server - apache or nginx.
@jayesheg - I tested LDoS on nginx. It easily crashes it within a few seconds.
Re:Slow rate denial of service attack for apache and mitigation on Wednesday October 05, 2011 @07:24AM (#3075149)
nginx should also be vulnerable, though one has better control over it, relatively. I have not yet tested full bloodedly against nginx, yet though. I will do that soon and publish.