New issue
Advanced search Search tips

Issue 716275 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 714824
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Can't import PKCS#12 file with empty password

Project Member Reported by cernekee@chromium.org, Apr 28 2017

Issue description

Chrome Version: 59.0.3065.0
OS: Chrome OS 9450.0

I normally create .P12 files like this:

$ openssl pkcs12 -export -out ovpn.p12 -inkey client1.key -in client1.crt -certfile ca.crt 
Enter Export Password: <hit enter>
Verifying - Enter Export Password: <hit enter again>

Prior to the MD UI changes, I was able to import these certs by entering a blank password in Chrome.  Post-MD, the OK button is grayed out until I enter at least one character, rendering my certs un-importable.

It would be ideal if the UI logic tried both permutations of "no password" (both "" and NULL) first, and then only prompted for a password if it was strictly needed.
 
Cc: dbeam@chromium.org
Components: -Internals>Network>Certificate UI>Browser
Labels: Proj-MaterialDesign-WebUI Proj-MaterialDesign-CrOS
Dan: It sounds like this is an MD-related regression. I tagged it both WebUI and CrOS since we use the same UI portion on Linux and CrOS (although CrOS has extra UI). I haven't been following MD-ification that closely, but do you know who would know about this?

The use case (an 'empty' password) is totally valid, so it sounds like someone just tied the OK button to the input accidentally :)

Comment 2 by dbeam@chromium.org, Apr 28 2017

Mergedinto: 714824
Owner: dpa...@chromium.org
Status: Duplicate (was: Untriaged)
already fixed and merged: https://codereview.chromium.org/2836143004/

Sign in to add a comment