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

On 22/12/16 14:30, Tom Delmas wrote: > There are other mechanisms. But hard to use, especially between > countries. As a Firefox user, > I expect that CA trusted by Firefox are clearly identifiable and > distinguishable from each others. If CAs ever did something specific to Firefox or the root

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

+richard=wosign@lists.mozilla.org] On Behalf Of Tom Delmas Sent: Thursday, December 22, 2016 10:30 PM To: Gervase Markham <g...@mozilla.org> Cc: mozilla-dev-security-pol...@lists.mozilla.org Subject: Re: wosign and letsencrypt.cn / letsencrypt.com.cn Hi Gerv, > It's never come up. But I

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

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: wosign and letsencrypt.cn / letsencrypt.com.cn

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

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

On Monday, December 19, 2016 at 2:45:16 AM UTC+1, Richard Wang wrote: > I wish everyone can talk about this case friendly and equally. I'm sorry about the wosing-bashing that followed. It wasn't my intention. > We know Let's Encrypt is released after the public announcement, but two day >

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

People here tend to bash WoSign/StartCom the whole time and make them guilty for nearly everthing, including the Lindbergh Kidnapping. I also do think people are actively searching for anything they can blame, and ignore/tolerate incidents of other CAs. Am Freitag, 16. Dezember 2016 19:18:27

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

在 2016年12月20日星期二 UTC+8下午8:21:33，Tom写道： > According to The Uniform Domain-Name Dispute-Resolution Policy, > letsencrypt.cn seem use in bad faith. > > On December 20, 2016 2:45:47 PM GMT+08:00, "谭晓生" wrote: > >It is ICP license you talked about, you can find some information

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

According to The Uniform Domain-Name Dispute-Resolution Policy, letsencrypt.cn seem use in bad faith. On December 20, 2016 2:45:47 PM GMT+08:00, "谭晓生" wrote: >It is ICP license you talked about, you can find some information here:

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

December 19, 2016 12:36 PM > To: mozilla-dev-security-pol...@lists.mozilla.org > Subject: Re: wosign and letsencrypt.cn / letsencrypt.com.cn > > We had some trouble figuring out how to purchase a Chinese domain name before > we launched, so we didn't purchase it then. We've never talke

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

. Best Regards, Richard -Original Message- From: dev-security-policy [mailto:dev-security-policy-bounces+richard=wosign@lists.mozilla.org] On Behalf Of j...@letsencrypt.org Sent: Monday, December 19, 2016 12:36 PM To: mozilla-dev-security-pol...@lists.mozilla.org Subject: Re: wosign

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

On Sunday, December 18, 2016 at 5:45:16 PM UTC-8, Richard Wang wrote: > I wish everyone can talk about this case friendly and equally. > > It is very common that everyone can register any domain based on the first > come and first service rule. > > We know Let's Encrypt is released after the

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

On Sunday, December 18, 2016 at 5:45:16 PM UTC-8, Richard Wang wrote: > We know Let's Encrypt is released after the public announcement, but two day > later, its .cn domain is still not registered, I think maybe it is caused by > the strict registration rule in China, so I registered it for

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

在 2016年12月19日星期一 UTC+8下午12:36:10，jo...@letsencrypt.org写道： > We had some trouble figuring out how to purchase a Chinese domain name before > we launched, so we didn't purchase it then. We've never talked to wosign > about this before, and we haven't seen the domain used for anything confusing >

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

We had some trouble figuring out how to purchase a Chinese domain name before we launched, so we didn't purchase it then. We've never talked to wosign about this before, and we haven't seen the domain used for anything confusing so far. This is our first interaction about it and we're happy to

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

I wish everyone can talk about this case friendly and equally. It is very common that everyone can register any domain based on the first come and first service rule. We know Let's Encrypt is released after the public announcement, but two day later, its .cn domain is still not registered, I

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

Well, based on the previous deception of WoSign before, during and after Mozilla's investigation, I'm not remotely surprised to see this. On Friday, December 16, 2016 at 10:18:27 AM UTC-8, tde...@gmail.com wrote: > It seams that wosign has registered the domains letsencrypt.cn and >