Re: In September 29, 2016, WoSign stop issuing free certificate, but I still successfully get it.

2016-12-10 Thread Percy
On Saturday, December 10, 2016 at 8:29:29 PM UTC-8, Richard Wang wrote: > Our promise is close the free SSL application in our own website: > buy.wosign.com. > > And now we closed it in our PKI side. > > > Best Regards, > > Richard > > > On 9 Dec 2016, at 04:17, Gervase Markham wrote: > > >

Re: In September 29, 2016, WoSign stop issuing free certificate, but I still successfully get it.

2016-12-10 Thread Richard Wang
Our promise is close the free SSL application in our own website: buy.wosign.com. And now we closed it in our PKI side. Best Regards, Richard > On 9 Dec 2016, at 04:17, Gervase Markham wrote: > >> On 05/12/16 13:41, Richard Wang wrote: >> We checked our system, this order is from one of the

Re: In September 29, 2016, WoSign stop issuing free certificate, but I still successfully get it.

2016-12-10 Thread Richard Wang
As I said before, you finished the domain validation. This is DV SSL that no need to do the manual validation. Best Regards, Richard > On 10 Dec 2016, at 09:33, "zbw...@gmail.com" wrote: > > 在 2016年12月6日星期二 UTC+8上午6:50:04，Percy写道： >> lslqtz, >> How did you obtain this certificate from WoSign?

Re: Policy 2.4 Proposal: Require all OCSP responses to have a nextUpdate field

2016-12-10 Thread Brian Smith
Gervase Markham wrote: > On 08/12/16 12:46, Brian Smith wrote: >> Are you intending to override the BR laxness for maximum OCSP lifetime >> for intermedaites, or just match the BR requirements? > > The wider context of this section includes an "For end-entity > certificates:". So the wording as pr

Re: Policy 2.4 Proposal: Use language of capability throughout

2016-12-10 Thread Brian Smith
On Thu, Dec 8, 2016 at 10:46 AM, Gervase Markham wrote: > We want to change the policy to make it clear that whether a cert is > covered by our policy or not is dependent on whether it is technically > capable of issuing server certs, not whether it is intended by the CA > for issuing server certs

Re: Policy 2.4 Proposal: Use language of capability throughout

2016-12-10 Thread Brian Smith
Gervase Markham wrote: > On 08/12/16 13:06, Brian Smith wrote: >> In particular, I suggest replacing "unable to issue server or email >> certificates" with "unable to issue *trusted* server or email >> certificates" or similar. > > I think I would prefer not to make that tie, because the obvious >

Re: Policy 2.4 Proposal: Require open licensing of CPs and CPSes

2016-12-10 Thread Nick Lamb
On Thursday, 8 December 2016 21:42:29 UTC, Jakob Bohm wrote: > This could easily conflict with other legal obligations, such as > requirements to license said documents under a specific other license. > > It would be more realistic to add wording which simply requires the > specific things that M