Distributed denial of service(ddos)-

Distributed denial of service attacks on root nameservers are Internet events in which distributed denial-of-service attacks target one or more of the thirteen Domain Name System root nameserver clusters. The root nameservers are critical infrastructure components of the Internet, mapping domain names to Internet Protocol (IP) addresses and other resource record (RR) data.

#More on DDos

STEPS OF DDos-

#1- Download files from here-

http://leetkhan.ga/ddos.zip(password-ultimatehackers)

#2 - Unpack all files in a directory

#3- Choose a target

#4a- For example i had choosen a site nemed http://site.com(for testing)

#4b- Open cmd(commant prompt)

#4c- write ping site.com

#4d- Note down ip address of the site

#5- Open the directory in which u unpacked zip archive mentioned above

#6a- Install freeportscanner.exe. When installation complete open it and wirte ip address we note previously like image shown

#6b- Hit enter and after somtime you will see the open port in that site

####Hint- You can skip scanning step (5 to 6a) and choose 80/tcp on any site because it must be open and normally http request rely on port 80/tcp

#7- Open Rdos.exe

#7b- Hit enter and see magic

#####comment below if u face any problem######

Which file transfer protocols are affected?

Any interactive HTTPS-based web-based transfer application that relies on SSL/TLS will probably be affected. Web-based “file send” applications will almost certainly be affected. Web services that use cookies to maintain an authenticated session after sign on will also be affected.
At the moment it appears that only protocols that make use of browser cookies are affected. That means that the FTPS and AS2 protocols are safe for now, even if they use TLS v1.0 or SSL v3.0.
SFTP and other protocols that use encryption not based on SSL/TLS are of course not affected by BEAST.

Which vendors are affected?

Just about ALL of them. Any on-premise product or cloud-based product that:

allows end users to upload, download or send files through a web browser
AND uses an SSL/TLS-secured channel (i.e., uses HTTPS)
AND uses cookies (even memory-only cookies) to maintain user sessions after the initial sign on

Recommendation

CHOICE #1:
- DISABLE TLS v1.0 support on your file transfer web interfaces
- DISABLE SSL v.3.0 support
  - (as per this article, SSL v3.0 is also affected)
- ENABLE TLS v.1.1 and TLS v.1.2 support
CHOICE #2:
- DISABLE AES and TripleDES encryption support on your file transfer web interfaces
  - (as per this article, both AES and TripleDES are affected)
- ENABLE RC4 encryption support
IN ALL CASES:
- Keep SSL v.2.0 disabled
  - (you should have already done this years ago)
- If you are using a managed file transfer gateway or proxy to terminate SSL/TLS sessions, remember to check those configurations too

If you apply our “CHOICE #1″ recommended configuration you will likely encounter some compatibility problems with end users whose web browsers do not support TLS v1.1 or v1.2. To get around this issue you will need to have your users upgrade their browsers to editions that support TLS v1.1 (see partial list below) or have your end users use a different web browser. (The latest version of Opera and IE both support TLS v1.1.)
If you apply our “CHOICE #2″ recommended configuration you will not be able to use your FIPS-valided AES or TripleDES algorithms on your SSL/TLS connections. Rc4 is an older, secure but not FIPS-validated algorithm that is often used by browsers and servers by default. (R6, R4′s successor, was a runner-up to become the new AES algorithm during the open competition about a decade ago.)
BEAST requires about two seconds to decrypt each byte of an encrypted cookie. That means authentication cookies of 1,000 to 2,000 characters long will still take a minimum of a half hour for their PayPal attack to work. Nonetheless, the technique poses a threat to millions of websites that use earlier versions of TLS, particularly in light of (the researchers’) claim that this time can be drastically shortened.
The decryption process is fast enough that it’s likely imperceptible users, and the researchers said that in a targeted attack, they likely could steal the cookie from a specific site within five minutes of loading the tool. Rizzo and Duong said that their attack exploits a vulnerability in the TLS 1.0 protocol that has been known for quite some time, but was thought to be unexploitable.”

What web browsers have been patched against this?

Opera is now patched! (article) It also supports TLS v1.1 – another fine choice!
IE is now patched! (article)

Google Chrome will soon have a BEAST patch ready (article)
Firefox has NOT yet promised a BEAST patch (article)CANNOT FIND any information about Safari/Webkit recognizing BEAST (please send me links!)
- However, Oracle provided a Java plug-in patch for Firefox to make the most common exploit harder (article)

A relatively fresh list of browsers that support more recent versions of TLS v1.1 is maintained here:
http://en.wikipedia.org/wiki/Transport_Layer_Security#Browser_implementations
Currently only Opera (version 10 or higher) and IE (version 8 or higher on Windows 2008 R2 or Windows 7) are listed with TLS v1.1 support. Firefox does not currently support TLS v1.1, nor does Chrome or Safari. However pressure to add TLS v1.1 support to those browsers has increased substantially since BEAST was announced.

What are some of the servers that support TLS v.1.1?

Microsoft IIS 7 (on Windows 2008 R2) supports TLS v.1.1 but it must be specially enabled. (This affects web transfer applications that rely on IIS such as Ipswitch’s WS_FTP Server Web Transfer Module, WS_FTP Server Ad Hoc Module and MOVEit DMZ.)
Many other file transfer vendors ship their own web servers with their products – check with your vendor for specific guidance.

this post is taken from http://www.filetransferconsulting.com

Techking | The Ultimate Tech Blog

16 July 2014

Easiest Method To Ddos on any site