Re: Proposal to Change the Default TLS Ciphersuites Offered by Browsers

Hi. let me add my comment for SEED. SEED was adopted to encourage escaping ActiveX dependency in Korea e-commerce environment. the impact of mozilla's effort was not figured out well. but it has meaning and VERY helpful for us to expand web standard environment (plugin free) at last year,

set default on for SHA2 for TLS1.1+ on firefox

Hi. currently SHA2 hash algorithm is used in TLS1.1 and 1.2 mozilla firefox is supporting it now. but the feature is set default off in latest firefox browser. can we set default ON for better security? Chrome is already enabled by default IE is trying to set default on from version 11 Opera is

Re: Proposal to Change the Default TLS Ciphersuites Offered by Browsers

let me add one more. SEED is normally used for TLS 1.1+ because the SSL Certificate issued from Korean CA use SHA2 hash algorithm. browser support for TLS 1.1 is limited currently. I expect that is one of the reasons why Korean web servers are not add SEED Cipher suites in SSL configuration.

Re: Proposal to Change the Default TLS Ciphersuites Offered by Browsers

-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto