Timeline for Authorize.net TLS Disablement Notice civicrm
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 19, 2017 at 2:41 | comment | added | Eli Lisseck | @harshal I asked it as a question because i'm not 100% sure if the curl command line tool uses the same library as the PHP CURL (provided by cURL project very confusing to me XD)... but if it were... it would be easier .. and I think it does. My server is using NSS and I double checked that the version number was post-TLS 1.2 support as per the blog post to be certain. | |
| Jul 19, 2017 at 1:55 | comment | added | harshal | @EliLisseck thanks for your comment which seemed to be very easy to test server compatibility with TLSv1.2 I used the curl howsmyssl.com and I get output as html page and I can see this particular html i.e. "<p><span class="label okay">Good</span> Your client is using TLS 1.2, the most modern version of the encryption protocol. It gives you access to the fastest, most secure encryption possible on the web.</p> " which says that my server is using TLS 1.2 so does that confirm that my environment is ready for the Authorize.net TLS1.1 disablement ? | |
| Jul 14, 2017 at 20:29 | comment | added | Eli Lisseck |
It's good that we have this blog post ... but I can see someone being very confused by the way it is presented. Anything wrong with just starting by curl https://www.howsmyssl.com and looking at the TLS version used to connect?
|
|
| Jul 14, 2017 at 16:07 | history | answered | Sean | CC BY-SA 3.0 |