jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 60733] server certificate change is restricted during renegotiation
Date Tue, 14 Feb 2017 16:55:38 GMT

Maverick <> changed:

           What    |Removed                     |Added
                 OS|                            |All

--- Comment #1 from Maverick <> ---
Application uses
The connection to this site uses a strong protocol (TLS 1.2), an obsolete key
exchange (RSA), and a strong cipher (AES_128_GCM).

And my JMeter Property file settings is

# SSL configuration

## SSL System properties are now in

# JMeter no longer converts property entries in this file into System
# These must now be defined in the file or on the
# The file gives more flexibility.

# By default, SSL session contexts are now created per-thread, rather than
being shared.
# The original behaviour can be enabled by setting the JMeter property:

# Default HTTPS protocol level:
# This may need to be changed here (or in to:

# List of protocols to enable. You may have to select only a subset if you find
issues with target server.
# This is needed when server does not support Socket version negotiation, this
can lead to:
# peer not authenticated
# Connection reset
# see
#https.socket.protocols=SSLv2Hello SSLv3 TLSv1

# Control if we allow reuse of cached SSL context between iterations
# set the value to 'false' to reset the SSL context each iteration

You are receiving this mail because:
You are the assignee for the bug.
View raw message