Although bug 383183 proposes to add a new primary chrome UI treatment for EV sites, it would be helpful to have a more low level display of the EV verification result. Maybe we could add something to Cert Viewer? I'd prefer a minimal change, with no chrome changes. Maybe, when you view a cert, you go to the details tab, you click the "certificate policies extension", which currently displays something like that: Not Critical 2.16.840.1.114413.1.7.23.3: Certification Practice Statement pointer: http://certificates.godaddy.com/repository This is a string. We could easily append more information here. Maybe add this line? Validated for EV Will it be clear what EV means? Should we spell it out? Cert Viewer can be used to view any cert. Is it correct to run the "is EV cert" test for any kind of cert, including CA certs?

I added such an implementation to the patch in bug 374336, trying to get it in at the same time.

(In reply to comment #0) > Although bug 383183 proposes to add a new primary chrome UI treatment for EV > sites, it would be helpful to have a more low level display of the EV > verification result. That's a good idea, adding EV information to Cert Viewer really makes sense! > I'd prefer a minimal change, with no chrome changes. > > Maybe, when you view a cert, you go to the details tab, you click the > "certificate policies extension", which currently displays something like that: > > Not Critical > 2.16.840.1.114413.1.7.23.3: > Certification Practice Statement pointer: > http://certificates.godaddy.com/repository > > This is a string. We could easily append more information here. On the one hand, it's a good place to put EV information here, but on the other hand it would mean that the "Certificate Fields" part of Cert Viewer would now also display some sort of "synthetic" bits (which might be confusing for those looking at this information, since they would possibly conclude that the "EV bit" is part of a certificate, actually). Wouldn't it make more sense to add EV information to the "General" tab (see bug 380775)? When looking at the mockup in attachment 264892 [details], it seems that Jonathan actually had the idea of putting a CP/CPS URL in there, so why not add some EV info, too?

Kaspar, there is also bug 378660 which talks about EV explicitly. I'm resolving this as fixed, because the patch in bug 374336 was checked in.