On Friday, November 24, 2017 at 5:36:20 PM UTC-6, Tom wrote:
> For information, WoSign/WoTrus can already sells WoSign-branded EV
> certificates accepted by major trusts stores, Mozilla's included.
>
> The intermediate certificate "WoSign EV SSL Pro CA" (
> https://crt.sh/?id=146206939 ) is
Nevertheless, WoTrus is (presumably) a commercial operation. Whoever owns that
organization bought or built it with an expectation of at least the possibility
of commercial success (profit). The organization's long term success requires
inclusion in major root programs.
For information,
On Friday, November 24, 2017 at 6:07:44 AM UTC-6, Gervase Markham wrote:
> While I do not want to make this discussion entirely about specific
> people, as Mozilla's investigator of the issues at the time I am
> satisfied that WoSign's actions at the time were taken with full
> knowledge - that
On 2017-11-22 21:10, Rob Stradling via dev-security-policy wrote:
> On 22/11/17 11:45, marcan via dev-security-policy wrote:
>> On 22/11/17 20:41, Tom via dev-security-policy wrote:
Although not listed in the Action plan in #1311824, it is noteworthy
that Richard Wang has apparently not
On 24/11/17 12:25, Gervase Markham via dev-security-policy wrote:
On 24/11/17 11:37, Rob Stradling wrote:
When issuing a "single domain" certificate to (for example)
www.example.com or *.example.com, it's fairly common practice for CAs to
also include in the certificate a SAN.dNSName for the
On 24/11/17 11:37, Rob Stradling wrote:
> When issuing a "single domain" certificate to (for example)
> www.example.com or *.example.com, it's fairly common practice for CAs to
> also include in the certificate a SAN.dNSName for the "base domain"
> (e.g., example.com). (Similarly, if the
6 matches
Mail list logo
