On Sun, Dec 20, 2020 at 9:54 AM Matthew Thompson via
dev-security-policy wrote:
>
> It's not ideal that Google Chrome now states "The connection to this site is
> using a valid, trusted server certificate issued by R3" (desktop) and "Google
> Chrome verified that R3 issued this website's
Definitely seems better for this issue, more identifiable to the user and
Firefox already does this for the padlock icon menu.
‐‐‐ Original Message ‐‐‐
On Sunday, 20 December 2020 17:04, Matthew Thompson via dev-security-policy
wrote:
> It's not ideal that Google Chrome now states
It's not ideal that Google Chrome now states "The connection to this site is
using a valid, trusted server certificate issued by R3" (desktop) and "Google
Chrome verified that R3 issued this website's certificate" (mobile). But that
seems to be an issue the Chromium project could resolve by
Sure, is there a more specific question I could answer? I'm not really sure
how to rephrase that, and CAs seem to understand it. [1]
[1] https://www.abetterinternet.org/documents/2020-ISRG-Annual-Report.pdf
On Fri, Dec 11, 2020 at 1:43 PM Burton wrote:
> Ryan,
>
> Please could you expand a
Ryan,
Please could you expand a little more on this?
"*Ideally, users would most benefit from simply having a random value in
the DN (no details, period) for both roots *and* intermediates, as this
metadata both can and should be addressed by CCADB"*
Burton
On Fri, 11 Dec 2020, 16:49 Ryan
On Fri, Dec 11, 2020 at 11:34 AM Burton wrote:
> The bits of information included in the CN field (company name, version,
> etc) created intermediate separation from the rest and the additional
> benefit of these bits of information included in the CN field in an
> intermediate was a person
The bits of information included in the CN field (company name, version,
etc) created intermediate separation from the rest and the additional
benefit of these bits of information included in the CN field in an
intermediate was a person could locate with some accuracy at first glance
the CA the
On Fri, Dec 11, 2020 at 5:51 AM Burton via dev-security-policy <
dev-security-policy@lists.mozilla.org> wrote:
> The common name of the Let's Encrypt R3 intermediate certificate (
> https://crt.sh/?id=3479778542) is in my opinion short and ambiguous. It
> doesn't have any information in common
Hi,
On Fri, 11 Dec 2020 10:51:44 +
Burton via dev-security-policy
wrote:
> The common name of the Let's Encrypt R3 intermediate certificate (
> https://crt.sh/?id=3479778542) is in my opinion short and ambiguous.
> It doesn't have any information in common name that can identify the
>
9 matches
Mail list logo
