Messages on Legacy are offline. Please check on SingSnap 2.0 or email us at support@singsnap.com for assistance.

Upgrade entire site to TLS 1.2

This topic is listed in Website Suggestions. It has been viewed 1,018 times and 10 replies have been made.

BCSchmerker2LEVEL 91

Post by BCSchmerker2GOLD

Running a series of passes with the Qualys® SSL Labs Client Transport Layer Test, I found that /Karaoke/Account/Login has already been upgraded to an HTTPS page with a TLS_ECDHE_RSA_AES256_CBC_SHA cipher algorithm. With routine server upgrades, I estimate that SingSnap® could run properly with an upgrade to a TLS_ECDHE_ECDSA_AES128_GCM_SHA256 algorithm with reasonably low performance penalty at the client end for all pages, plus files at the SingSnap® Media, Songs, and Recording servers. (TLS_ECDHE_ECDSA_AES256_GCM_SHA384 would be more crack-resistant, but performance would probably take too much of a hit.) Can this be done in time for a crertificate renewal at Thawte® (ideally before mid-May 2017)?

ZZ-EdLEVEL 67

Reply by ZZ-EdGOLD

I can remember when this used to be FUN...

^ What he said...

CanadaBlonde

Edited reply by CanadaBlondeGOLD

I agree.

Generic121618

Edited reply by Generic121618

Can this be done in time for a crertificate renewal at Thawte® (ideally before mid-May 2017)?BCSchmerker2

As trivial as this cipher change is.. (yes i know, better encryption.. CBC is good, GMC is better so there's not a real world benefit here.. yet)
as long as you still use your logon session on an insecure site (read: https is redirected to http for the vast majority of the site) there really isnt a point in upgrading a cipher suite.
Only the logon page and the payment pages are secure which makes no sense at all as the session is carried over to the nonsecure portion of the website; if my session is compromised on the insecure part of the site it can be reused on the secure part; they leave the option for a man in the middle attack wide open.
It's nice to add another chain to the link (preferring gmc over cbc) but it's probably wise to fix the weakest link first.

BCSchmerker2LEVEL 91

Reply by BCSchmerker2GOLD

My point exactly. After further research into usable processes for streams, it appears that the SingSnap® Songs and Recording might work better with the TLS_ECDHE_ECDSA_CHACHA20_POLY1304_SHA256 cipher, which was developed for streaming content over the Internet (whereas TLS_ECDHE_ECDSA_AES128_GCM_SHA256 was developed for block content).

BCSchmerker2LEVEL 91

Reply by BCSchmerker2GOLD

Update: I am currently running tests with Mozilla® Firefox® 52.0 on the Hot Rod gPC™. Transport Layer Security 1.3 is approaching release candidacy as of January 2017, and a number of older cipher suites are on the chopping block; among the old CBC cipher suites, only TLS_RSA_WITH_AES_128_CBC_SHA will be retained for purpose of setting up session secrets. Don't think TLS 1.3 will be published before mid-year, but recommend Per begin tests with TLS_ECDHE_ECC_WITH_AES_128_GCM_SHA256 for photos and text and TLS_ECDHE_ECC_WITH_CHACHA20_POLY1305_SHA256 for audio and video. (Cloudflare® has a TLS 1.3 test page running with TLS_AES_128_GCM_SHA256 cipher and three ECC certificates issued by Comodo Canada, Limited.)

BCSchmerker2LEVEL 91

Edited reply by BCSchmerker2GOLD

Erratum for post 5: The SingSnap® BBC engine stripped the HTTPS call from the "TLS 1.3 test page" hyperlink; the Cloudflare® server fills insecure calls to http://tls13.cloudflare.com using Hyper-Text Transmission Protocol 1.1.

BCSchmerker2LEVEL 91

Reply by BCSchmerker2GOLD

Update 2: The Internet Engineering Task Force planning to deprecate AES_CBC ciphers and RSA_SHA1 certificates for TLS 1.3, recommend Per also begin tests with TLS_ECDHE_ECC_WITH_AES_256_GCM_SHA384 for transaction functions currently on the TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA cipher suite.

The IETF is writing curve25519 into the ECDHE specification for the TLS 1.3 key exchange (as an alternate to United States elliptic curve specifications SECP256R1, SECP384R1, and SECP521R1) as I write this; if Thawte® can encode the next set of Certificates in ECC_256_SHA512/ED25519 (as Comodo is already doing for some CloudFlare® clients), SingSnap® will be ready when TLS 1.3 is published, barring server-configuration problems.

BCSchmerker2LEVEL 91

Reply by BCSchmerker2GOLD

Update 3: After tuning my own Mozilla® Firefox® 52.0 installation on the ASUS® CM1630-06 as upgraded under Microsoft® Windows® 10 Version 1607 10.0.14393.693, I am recommending the following settings at server level, based on the Qualys® SSL Labs™ Client Test:

Protocol: TLS 1.2.
Cipher Suites
- Text and Photos: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256.
- Streaming Audio/Video: TLS_ECDHA_ECDSA_WITH_CHACHA20_POLY1305_SHA256.
- Secure Transactions: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384.
Protocol Details
- Server Name Indication: Yes
- Secure Renegotiation: Yes
- TLS Compression: No
- Session Tickets: Yes
- OCSP Stapling: Yes
- Signature algorithms: SHA256/ECDSA; SHA384/ECDSA; SHA512/ECDSA; SHA256/RSA; SHA384/RSA; SHA512/RSA.
- Elliptic Curves: secp256r1, secp384r1, secp521r1.
- Application Layer Protocol: HTTP 2.0.

TLS 1.3 is still in alpha as of 9 March 2017, but the following adjustments would be appropriate when enacted:

Protocol: TLS 1.3.
Cipher Suites
- Text and Photos: TLS_AES_128_GCM_SHA256.
- Streaming Audio/Video: TLS_CHACHA20_POLY1305_SHA256.
- Secure Transactions: TLS_AES_256_GCM_SHA384.
Protocol Details
- Signature algorithms: RSA_PSS_SHA256; RSA_PSS_SHA384; RSA_PSS_SHA512; SHA256/ECDSA; SHA384/ECDSA; SHA256/RSA; SHA384/RSA.
- Elliptic Curves: x25519, secp256r1, secp384r1, secp521r1.

BCSchmerker2LEVEL 91

Edited reply by BCSchmerker2GOLD

CRUNCH TIME! Transport Layer Security 1.3 is now up to release candidate, as shown this proposed Specification from the Internet Engineering Task Force. Taking into consideration older systems used by advertisers, recommend the following as part of the full TLS implementation here at SingSnap®:

Protocol: TLS 1.2.
Key exchange: Enhanced Diffie-Hellman Ephemeral. Existing profiles are elliptic-curve (United States ECC's SECP256R1, SECP384R1, SECP521R1); recommend adding twisted-Edwards curve x25519 per TLS 1.3 RC.
Authentication: RSA_4096_PSS_SHA256, RSA_8192_PSS_SHA512, ECC_256_SHA256, ECC_384_SHA384, ECC_512_SHA512. Recommend adding Ed25519 twisted-Edwards-curve authenticator protocol to SECP's listed in Key Exchange above. Also recommend extended validation of Certificate, with Singsnap Corporation (CAN) as issuee.
Bulk Ciphers by Subsite
- Main: TLS_ECDHE_ECDSA_AES_128_GCM_SHA256 except Payments TLS_ECDHE_ECDSA_AES_256_GCM_SHA384.
- Media: TLS_ECDHE_ECDSA_AES_128_GCM_SHA256.
- Songs: TLS_ECDHE_ECDSA_CHACHA20_POLY1305_SHA256.
- Recordingnn: TLS_ECDHE_ECDSA_CHACHA20_POLY1305_SHA256.

BCSchmerker2LEVEL 91

Reply by BCSchmerker2GOLD

EPILOGUE: As of 10 December 2020, SingSnap® 2.0 is operational. Login at this point.

B. C. Schmerker