Re: Mozilla Team-about the upcoming branding changes at Symantec/VeriSign, and working to implement them in Mozilla/Firefox

2012-03-09 Thread ianG
On 10/03/12 04:56 AM, Brian Smith wrote: Geoffrey Noakes wrote: The *only* change we are asking of Mozilla is to change "Verified by: VeriSign, Inc." in the hover-over box to "Verified by Norton": In Firefox, we show the name of the organization that issued the intermediate certificate (the

Re: Mozilla Team-about the upcoming branding changes at Symantec/VeriSign, and working to implement them in Mozilla/Firefox

2012-03-09 Thread Wan-Teh Chang
On Fri, Mar 9, 2012 at 9:56 AM, Brian Smith wrote: > > The second question is: Should we change the string in the display of the > *root* certificate from "VeriSign, Inc." to "Norton." Ideally this string should come from the certificate. The fundamental purpose of a certificate is to bind a pu

Re: Mozilla Team-about the upcoming branding changes at Symantec/VeriSign, and working to implement them in Mozilla/Firefox

2012-03-09 Thread Eddy Nigg
On 03/09/2012 07:56 PM, From Brian Smith: If others agree, then I will file a bug about implementing a change to display the O= field from all CA certificates in the chain in this UI. My question would be how you would do that, is there enough UI real estate for that? If there is, it would be

Re: Mozilla Team-about the upcoming branding changes at Symantec/VeriSign, and working to implement them in Mozilla/Firefox

2012-03-09 Thread Brian Smith
Geoffrey Noakes wrote: > > The *only* change we are asking of Mozilla is to change "Verified by: > VeriSign, Inc." in the hover-over box to "Verified by Norton": In Firefox, we show the name of the organization that issued the intermediate certificate (the subject O= field of the intermediate ce

Problem with intermediate CAs

2012-03-09 Thread Helge Bragstad
Hello, I bought a code signing certificate from DigiCert, but then stumbled over this one: https://bugzilla.mozilla.org/show_bug.cgi?id=321156 I can't be the first, so I wonder if there are any workarounds since this problem has not been yet fixed? Regards, Helge Bragstad -- dev-tech-crypto