Gemalto is now part of the Thales Group, find out more.

You are here

HTTPS TCP Connection - Migration to SSLV3 broke out System | Thales IoT Developer Community

April 12, 2017 - 1:38pm, 6902 views

I've developed an application that communicates with a web page via TCP. Passing the url, I'm using "https://.." and this has worked smoothly in SSLV2 without having to deal with certificates and such. Thing is, our hosting provider has updated the platform to SSLV3 and the system started to fail the communication, presenting the following messages: Subject alternative name did not match site name

-, bci=642

-, bci=108

-, bci=7

-, bci=33

-, bci=3

-, bci=5

For now, the hosting company kept us a port with SSLV2 but we need to work this out for the update.

So, what measures should I take migrate my system into SSLV3?