Hosting Site says PCI deadline pushed back to 2018, not supporting TLS 1.2 yet
-
Dear David, I am new to your forum, and first want to thank you for the work on Seamless Donations. I really like this solution for the non-profit I am working with.
However, BLUEHOST.COM indicates PCI requirement to move to TLS 1.2 has been pushed to 2018 and consequently they will not be upgrading in the near future the TLS / cURL / OpenSSL versions.There suggestion was to consider using a different donation Plug-in (see attached transcript).
My questions to you
1. Is there any workaround for now with the current version of Seamless Donations and my hosting provider… seems we are at an impasse. ?2. Is there any option for me to obtain a prior version of Seamless Donations and use this until BlueHost.com upgrades their versions of those products? I desire to continue to use Seamless Donations and PayPal standard for the payment processor for donations.
Thank you for your continued support to the product and the community.
Today’s CHAT with BLUEHOST.COM tech support:
QUESTION:Though we recently upgraded and had installed COMODO SSL, along with a dedicated IP address, that did not resolve the problem….. Can BlueHost to upgrade the the site so that we are compliant with the requirements for the Plug-in and Paypal:
– OpenSSL 1.0.1 or greater
– TLSv1.2,
– cURL 7.34.0 or greater— Thank you for any assistance
(15:5) [Rameez] Hello, thank you for contacting support. I apologize for the wait time. Your patience is greatly appreciated.
….
(15:15) [Rameez] I have contacted our specialist to look into this issue, so waiting for response
….
(15:20) [Rameez] The PCI deadline for transitioning away from TLS 1.0 has been pushed back to 2018. This means that we do not need to force inbound connections to TLS 1.2 yet. However, 3rd parties may still require TLS 1.1 and 1.2 protection for outbound connections which we offer alternative hosting platforms for.
(15:20) [Rameez] Since there are still a large number of devices that will only support TLS 1.0 or older, it isn’t likely that this update will roll out very quickly. For Q2 in 2016, we anticipate no, or very low, customer impact.
(15:20) [Rameez] Enterprise System Operations is requesting you report any TLS 1.0 compatibility issues, seen in any of your support channels, via the form linked to below. We are in the process of gathering data for our TLS Remediation Initiative which will take place in Q4 2016 and Q1 2017.
(15:24) [Craig Deaton on beha] OK. as it stands now the SEAMLESS DONATION WordPress Plugin and its developer is requiring TLS 1.2 – Is there a path today for our site to continue to use SEAMLESS DONATIONs (can it be updated to TLS 1.2 et al, or must I look for another donation plugin?
(15:27) [Craig Deaton on beha] Secondly, I had discussed this issue with another BlueHost.Com tech support rept severals ago and he indicated the need to install an SSL certificate and a dedicated IP would resolve the problem…. He did not advise me of the TLS 1.2 not being supported for some time.
(15:27) [Rameez] I would recommend you use another plugin .
(15:29) [Craig Deaton on beha] Well that is not the answer I wanted to here ;-( but will pursue that direction
(15:30) [Rameez] Sorry that is not answer from me directly, It is from our specialist
(15:31) [Craig Deaton on beha] Understood Rameez, I appreciate the help.. I will share this information with the plug-in developer to see if he has a supported option for me. Thanks
(15:31) [Rameez] My Pleasure.
(15:31) [Rameez] Is there anything else I can help with for now?
(15:32) [Craig Deaton on beha] Not today, thanks again,
- The topic ‘Hosting Site says PCI deadline pushed back to 2018, not supporting TLS 1.2 yet’ is closed to new replies.
