OU component in certificate viewer differs by platform when multiple OU's in certificate
Reported by
mccarthy...@gmail.com,
Aug 22
|
||||||
Issue description
Chrome Version : 68.0.3440.106
URLs (if applicable) : timaru.govt.nz
Other browsers tested:
Firefox: Firefox doesn't display OU easily like Chrome does. If you drill down 4 clicks into cert details Firefox shows the correct "IT Department". AFAIK there is no way to view cert details in Firefox Android.
What steps will reproduce the problem?
1. On Chrome Dev Android 70.0.3522.0 visit a website such as timaru.govt.nz. In the certificate viewer the OU is "COMODO EV SSL"
2. On Chrome Linux 68.0.3440.106 visit the same site and the other OU "IT Department" is shown.
What is the expected result?
Consistency across platforms would be nice. "IT Department" is the correct OU here but I don't see how Chrome would decide that. The OU in general is filled with so much junk that it may not be worth effort to change though.
What happens instead of that?
Chrome Android and Chrome Linux choose different OU to display when multiple OU in cert.
Please provide any additional information below. Attach a screenshot if
possible.
This issue appears on any certificate that has multiple OU's such as:
agrobro.ro
login.gamestop.com
See the cert at
https://crt.sh/?q=E6AB2A5A8901390F261807A1A0F8E835C6A46965
,
Aug 23
,
Aug 23
Thanks for filing the issue! From the comment#0 it is understood that the issue is with Android, hence adding appropriate OS label and requesting some one from respective team to have a look into this. Note: Tentatively adding component "UI>Browser>CertificateViewer" please change if this isn't apt.
,
Aug 24
,
Aug 24
Tested the issue in Android and able to reproduce the issue. Steps to Reproduce 1. Open a chrome and navigated to timaru.govt.nz 2. Opened certificate viewer and observed "COMODO EV SSL" instead of "IT Department" Chrome versions: 60.0.3072.0, 68.0.3440.91, 70.0.3530.0 OS: Android 9.0 Android Devices: Pixel 2 XL This issue is seen from M-60 older builds, hence considering this issue as Non-Regression and marking as untriaged. Thanks!
,
Aug 24
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by susan.boorgula@chromium.org
, Aug 23