Author

Topic: SSL changes 2015-07-23T00:00UTC (Read 600 times)

legendary
Activity: 2128
Merit: 1073
July 22, 2015, 07:38:28 PM
#3
This error reoccurred, this time not involving older Macintoshes, but up-to-date patched, clean, unmodified Windows with Internet Explorer 11:

Quote
Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://bitcointalk.org  again. If this error persists, contact your site administrator.

All those protocols were already enabled, and this time I'm positive that my ISPs (plural ISPs) were all working correctly and there wasn't man-in-the-middle or any other shenanigans going on.

The time stamp are in the range:

2015-07-23T00:00 UTC

to

2015-07-23T00:31 UTC

and this time I ran several tests on various ISPs and various OS installations.

administrator
Activity: 5222
Merit: 13032
March 31, 2015, 05:46:07 PM
#2
The *.bitcointalk.org cert (used for the image proxy) was renewed a day or two ago. The actual RSA key didn't change. I didn't change the supported cipher suites. The certificate authority does signing using SHA-256 instead of SHA-1 now, though.
legendary
Activity: 2128
Merit: 1073
March 31, 2015, 03:08:49 PM
#1
Some of older computers (older Macintoshes) can no longer access bitcointalk because they can't establish a secure connection HTTPS/SSL.

Can you tell us what did you change at that time?

Can you maybe re-enable some lower security transport protocols?

Edit: Hmm, it is back to loading pages and working OK. The current date stamp is 2015-03-31T20:21 .

Edit2: Editing just a title to refer to the reoccurrence of the errors.
Jump to: