Comment #7 on issue 28673 by [email protected]: Can't convince Chrome that my Tivo's self signed certificate is ok http://code.google.com/p/chromium/issues/detail?id=28673
rspier: could you attach your Tivo certificate to this bug report or email it to me? I'd like to inspect your Tivo certificate to see if it contains any unsual field or extension. I just used the apache2-ssl-certificate command to generate a self-signed certificate for a server. I found that I have to use the trust flags "C,," on it. (Note: trust for code signing is irrelevant for this bug.) If I use the trust flags "P,," on it, Chrome still reports it as not trusted. I then used Firefox to add a "security exception" for that certificate. I found that Firefox didn't set any trust flags on it. So Firefox must store some info outside the NSS databases about its "security exceptions". -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
