View Single Post
Old 02-15-2019, 12:07 AM   #20
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,114
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Sheesh... Basically, Kobo is dropping support for SSL 3.1 and TLS 1.0. If your device/application can handle TLS 1.2 or higher, you won't see an issue.

As to why they are dropping support? SSL 3.0 and TLS 1.0 are no longer considered secure. TLS 1.1 is also going to hit the dustbin in early 2020. For what it's worth, since Jan. 1, 2019, over 93% of my website connections have used TLS 1.2 or 1.3. Probably because the PCI Data Security Standard mandated no SSL 3.0/TLS 1.0 by June 30, 2018 and recommended not using TLS 1.1.
Attached Thumbnails
Click image for larger version

Name:	mobileread_encryption.jpg
Views:	379
Size:	83.0 KB
ID:	169727  
DNSB is offline   Reply With Quote