# POODLE/SSLV3

**URL:** <https://community.gatling.io/t/poodle-sslv3/1547>\
**Category:** Gatling (Open-Source)\
**Created:** [October 15, 2014, 2:03pm UTC](https://community.gatling.io/t/poodle-sslv3/1547 "2014-10-15T14:03:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastien\_Cavecchi](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Sebastien\_Cavecchi](https://community.gatling.io/u/Sebastien_Cavecchi)\
**Post date:** [October 15, 2014, 2:03pm UTC](https://community.gatling.io/t/poodle-sslv3/1547/1 "2014-10-15T14:03:35Z")

</div>

Hi,

Since we SSLV3 disabled (because POODLE ) on our application, our tests make gatling handshake\_failure How do I disable SSLV3 of gatling please ?

“javax.net.ssl.SSLException: Received fatal alert: handshake\_failure”

Regards ,

Sébastien

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [October 15, 2014, 2:11pm UTC](https://community.gatling.io/t/poodle-sslv3/1547/2 "2014-10-15T14:11:06Z")

</div>

Ah ah ah ah ah.

Not supported ATM.

This would require me to patch AsyncHttpClient, then Gatling.

---

<div class="post-metadata">

**Author:** ![Sebastien\_Cavecchi](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Sebastien\_Cavecchi](https://community.gatling.io/u/Sebastien_Cavecchi)\
**Post date:** [October 15, 2014, 2:18pm UTC](https://community.gatling.io/t/poodle-sslv3/1547/3 "2014-10-15T14:18:00Z")

</div>

Merdum,

Merci Stéphane.

Vs avez prévu de le faire ?

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [October 15, 2014, 2:25pm UTC](https://community.gatling.io/t/poodle-sslv3/1547/4 "2014-10-15T14:25:39Z")

</div>

What happens exactly? Which protocols does your server still support?  
We use standard JSSE provider, that supports SSLv3 and TLSv1. I would expect it to pick TLSv1 if server doesn’t support SSLv3.

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [October 15, 2014, 2:42pm UTC](https://community.gatling.io/t/poodle-sslv3/1547/5 "2014-10-15T14:42:29Z")

</div>

There’s a good chance the problem is on your side.  
I just tested with a server that has only TLSv1 enabled and Gatling/AsyncHttpClient works properly as expected.

---

<div class="post-metadata">

**Author:** ![Sebastien\_Cavecchi](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Sebastien\_Cavecchi](https://community.gatling.io/u/Sebastien_Cavecchi)\
**Post date:** [October 15, 2014, 3:08pm UTC](https://community.gatling.io/t/poodle-sslv3/1547/6 "2014-10-15T15:08:19Z")

</div>

We have this problem only on Websocket server that accept TLSv1+HIGH

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [October 15, 2014, 3:36pm UTC](https://community.gatling.io/t/poodle-sslv3/1547/7 "2014-10-15T15:36:50Z")

</div>

Not an OpenSSL expert, but it looks to me that your issue is not with the transport (TLS) but with the cyphers.  
+HIGH means keys longer than 128 bits.  
If so, you’d have to install [JCE](http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html) as Java comes by default with limited cryptography, as of american laws.

If that doesn’t do the trick, let’s be honest: I can’t provide more help without consulting.

---

<div class="post-metadata">

**Author:** ![Sebastien\_Cavecchi](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Sebastien\_Cavecchi](https://community.gatling.io/u/Sebastien_Cavecchi)\
**Post date:** [October 16, 2014, 7:17am UTC](https://community.gatling.io/t/poodle-sslv3/1547/8 "2014-10-16T07:17:03Z")

</div>

Problem Solved

Shared Information:  
TLS 1.1 / 1.2 are not enabled by default in java7.  
To enable and disable SSLv3, add in JAVA options:  
-Ddeployment.security.SSLv2Hello -Ddeployment.security.SSLv3 = False = false = false -Ddeployment.security.TLSv1 -Ddeployment.security.TLSv1.1 -Ddeployment.security.TLSv1.2 = true = true

In java8, is enabled by default TLS1.2

---

<div class="post-metadata">

**Author:** ![Sebastien\_Cavecchi](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Sebastien\_Cavecchi](https://community.gatling.io/u/Sebastien_Cavecchi)\
**Post date:** [October 16, 2014, 7:33am UTC](https://community.gatling.io/t/poodle-sslv3/1547/9 "2014-10-16T07:33:45Z")

</div>

sorry for bad copy/paste  
-Ddeployment.security.SSLv2Hello=false -Ddeployment.security.SSLv3=false -Ddeployment.security.TLSv1=false -Ddeployment.security.TLSv1.1=true -Ddeployment.security.TLSv1.2=true