Issue metadata
Sign in to add a comment
|
Problem with Digital Certificate with letter &
Reported by
victor.s...@gmail.com,
Oct 9 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: I have a problem with the new version of Chrome, I have a digital certificate with a Applicant is OU = AR V & G Is it possible that the character "&" generate error? Because the certificate is not listed in the browser, however in Firefox and IE normally. In older versions of Chrome it works normal. I only have issue with this certificate others work normally, and only in this version of Google Chrome. What is the expected behavior? What went wrong? The certificate is not listed. Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version:
,
Oct 9 2017
Can you please provide a Network Log, as described at https://dev.chromium.org/for-testers/providing-network-details ? Can you indicate whether you're trying to use this as a Client Certificate or a Server Certificate? From the screenshot, I would guess client certificate, but would want to confirm. It's possible that this is a regression due to Chrome improving its spec compliance with respect to certificates - improperly encoded certificates are not presented to the user anymore. If the CA has failed to adhere to the proper specifications, this would potentially cause issue.
,
Oct 9 2017
,
Oct 9 2017
Hi, It is a client certificate, I took the network test to enter the site requesting the certificate. The same was not presented for selection. This happens only in this new chrome, IE and Firefox work normally.
,
Oct 9 2017
Thank you for providing more feedback. Adding requester "rsleevi@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 9 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by b...@chromium.org
, Oct 9 2017