TLS Renegotiation Test

3 Comments

The new TLS/SSL man-in-the-middle (MiTM) attack targets the renegotiation part of the protocol. There are two variations of the renegotiation – client initiated and server initiated. This tool allows you to test any web server (input as server:port) for client initiated renegotiation support, as server initiated renegotiation depends on specific server configuration. As currently there is no fix other than disabling renegotiation, this will pretty much tell you whether the server is vulnerable or not to this type of renegotiation attack

Tags: , , , , , , ,

3 Responses to “TLS Renegotiation Test”

  1. Tweets that mention TLS Renegotiation Test | netsekure rng -- Topsy.com Says:

    [...] This post was mentioned on Twitter by PhoneFactor, Marsh Ray. Marsh Ray said: RT @naskooskov TLS client initiated renegotiation test http://netsekure.org/2009/11/tls-renegotiation-test/ [...]

  2. Extended Subset » Blog Archive » Assorted news Says:

    [...] has set up a nice test for client-initiated renegotiation on his blog. This is probably the most pervasive, and simplest to exploit, form of the SSL/TLS [...]

  3. MitM Plaintext Injection Vulnerability in TLS (openssl) « waffle Says:

    [...] Test Here: TLS Renegotiation Test | netsekure rng [...]