Re: Intermediate common name ambiguous naming

2020-12-20 Thread Peter Bowen via dev-security-policy
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

RE: Summary of Camerfirma's Compliance Issues

2020-12-20 Thread Ramiro Muñoz via dev-security-policy
Hi Ben, Ryan, Burton and all: Camerfirma will present its claims based on a description of the problems found by associating the references to the specific bugs. After making a complete analysis of the bugs as presented by Ben, always considering that bugs are the main source of truth, we see

Re: Intermediate common name ambiguous naming

2020-12-20 Thread Matthew Thompson via dev-security-policy
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

Re: Intermediate common name ambiguous naming

2020-12-20 Thread George via dev-security-policy
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