RE: wosign and letsencrypt.cn / letsencrypt.com.cn

2016-12-22 Thread Richard Wang
In this case, no any CA named as letsencrypt similar name, and no any CA want to impersonate, most CA program require the root CA have a unique friendly name in the CA program. Best Regards, Richard -Original Message- From: dev-security-policy

Re: Firefox 50.1.0 still does not offer any secure SSL / TLS ciphers

2016-12-22 Thread Eric Rescorla
On Wed, Dec 21, 2016 at 11:58 PM, wrote: > Hi all, > > I already have reported the following issue in the bug tracking system and > now have been told that the bug has been closed and that I should put it > for discussion here. > > Please note that I am no way a security expert,

Re: wosign and letsencrypt.cn / letsencrypt.com.cn

2016-12-22 Thread Tom Delmas
Hi Gerv, > It's never come up. But I think we would be reluctant to intervene; Thank you for that answer. I understand it. > there are other mechanisms for sorting out such disputes, and it's not > our job to interpret or enforce trademark law or domain name dispute > resolution law. There are

Re: Firefox 50.1.0 still does not offer any secure SSL / TLS ciphers

2016-12-22 Thread Kurt Roeckx
On 2016-12-22 08:58, i...@binarus.de wrote: Hi all, I already have reported the following issue in the bug tracking system and now have been told that the bug has been closed and that I should put it for discussion here. Please note that I am no way a security expert, so please don't blame

Re: wosign and letsencrypt.cn / letsencrypt.com.cn

2016-12-22 Thread Gervase Markham
On 21/12/16 12:42, tdel...@gmail.com wrote: > I think Mozilla still doesn't answer my first question:what is the > position of Mozilla regarding CA that act in bad faith regarding the > usage of the names associated with others CA (like, registering such > trademarks or domains) ? It's never come

Firefox 50.1.0 still does not offer any secure SSL / TLS ciphers

2016-12-22 Thread info
Hi all, I already have reported the following issue in the bug tracking system and now have been told that the bug has been closed and that I should put it for discussion here. Please note that I am no way a security expert, so please don't blame me if the following is wrong. But I am sort of