Bitcoin Forum
July 29, 2021, 07:51:33 PM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: SSL changes 2015-07-23T00:00UTC  (Read 547 times)
2112
Legendary
*
Offline Offline

Activity: 2128
Merit: 1038



View Profile
March 31, 2015, 08:08:49 PM
Last edit: July 23, 2015, 12:53:33 AM by 2112
 #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.

Please comment, critique, criticize or ridicule BIP 2112: https://bitcointalk.org/index.php?topic=54382.0
Long-term mining prognosis: https://bitcointalk.org/index.php?topic=91101.0
1627588293
Hero Member
*
Offline Offline

Posts: 1627588293

View Profile Personal Message (Offline)

Ignore
1627588293
Reply with quote  #2

1627588293
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
theymos
Administrator
Legendary
*
Offline Offline

Activity: 4186
Merit: 8574


View Profile
March 31, 2015, 10: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.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
2112
Legendary
*
Offline Offline

Activity: 2128
Merit: 1038



View Profile
July 23, 2015, 12:38:28 AM
 #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.


Please comment, critique, criticize or ridicule BIP 2112: https://bitcointalk.org/index.php?topic=54382.0
Long-term mining prognosis: https://bitcointalk.org/index.php?topic=91101.0
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!