New issue
Advanced search Search tips

Issue 720349 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome crashes to desktop when I try to use or see a SSL certificate

Reported by fbonill...@gmail.com, May 10 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Enter an official secure site (government, etc.)
2. Try to login using a personal SSL certificate
3. Instead of popping a prompt asking to select a certificate, it CTDs.

It also happens if I access to config and watch the certificates there. As soon as I leave, Chrome CTDs.

Also

What is the expected behavior?
A selection window with several personal certificates should appear so I can choose one. Then I should be logged in those secure sites.

What went wrong?
Well, I can't use Chrome anymore for any official procedure that requires to login through a personal certificate, because Chrome crashes immediately every time.

Crashed report ID: f1a6a265-b7c7-44a5-9e12-ff80655b8faa

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes Well, it worked until yesterday. Don't know more.

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: 

I don't use any antivirus but the one Windows 10 uses by default. Haven't installed anything (that I know of) before it started failing.
 
Cc: ligim...@chromium.org
Labels: Needs-Triage-M58 Needs-Feedback
Please provide the website which crashed. Also provide the server id from chrome://crashes for investigating further.

Components: Internals>Network>Certificate

Comment 3 by mmenke@chromium.org, Jun 14 2017

[fbonilladc]:  It's been a month without a followup, so closing the bug.  Feel free to file a new bug, with the requested information.
Status: WontFix (was: Unconfirmed)
Actually closing the bug as suggested in c#3 :-}.

Sign in to add a comment