Hi Ryan,
thanks for your enlightening feedback to my poor comments... let me try to add
some more here.
El lunes, 30 de abril de 2018, 17:22:38 (UTC+2), Ryan Sleevi escribió:
> On Sun, Apr 29, 2018 at 10:12 AM, pfuentes69--- via dev-security-policy <
> dev-security-policy@lists.mo
e replaced so that the old intermediate (without a
> constraint on srvName) can be revoked?
>
> On Mon, Apr 23, 2018 at 3:42 PM, Wayne Thayer via dev-security-policy <
> > dev-security-policy@lists.mozilla.org> wrote:
> >
> >> On Sun, Apr 22, 2018 at 2:56 PM
I think you should consider an an exception Issuing CAs including Name
Constraints. This would keep allowing root signing services for corporate CAs
without forcing multiple CAs.
El viernes, 20 de abril de 2018, 23:03:17 (UTC+2), Wayne Thayer escribió:
> On Thu, Apr 19, 2018 at 8:40 PM, Jakob B
Dear Andrey,
In the future GB will replace GA, and GC is ECC.
This replacement means that new SubCAs will be under GB, but GA must stay alive
as long as there are active CAs under it, which will be still some years from
now.
Best,
Pedro
___
dev-securi
Sorry, obviously I meant "we can't control..."
It seems that the address I used yesterday to answer is not enabled in this
list. What I said yesterday was to state the following:
1. The contact information for WISeKey certification services is the specified
in our CPS and in the CCADB. The addr
I sent yesterday an answer to this in behalf of Wisekey but it’s not been
published.
We can control if all customers configure properly their servers. The only one
I found (https://mail.egov.sc/OWA) seems to be OK.
___
dev-security-policy mailing li
6 matches
Mail list logo
