Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
[Deleted User] <[Deleted User]> #3
dh...@chromium.org <dh...@chromium.org> #4
[Empty comment from Monorail migration]
rs...@chromium.org <rs...@chromium.org> #5
We removed support for --use-system-ssl some time ago, as it presented risks to security, stability, and speed, and have no plans to re-introduce it.
It would be good if you can indicate exactly what Smartcard and Smart Card middleware you're using. If this is a national ID card, a reference to the national ID website that we can look into things further would be great.
It would be good if you can indicate exactly what Smartcard and Smart Card middleware you're using. If this is a national ID card, a reference to the national ID website that we can look into things further would be great.
rs...@chromium.org <rs...@chromium.org> #6
[Empty comment from Monorail migration]
we...@gmail.com <we...@gmail.com> #7
[Comment Deleted]
we...@gmail.com <we...@gmail.com> #8
[Comment Deleted]
we...@gmail.com <we...@gmail.com> #9
[Comment Deleted]
we...@gmail.com <we...@gmail.com> #10
We are using the clauer project software http://clauer.nisu.org/ with self signed certificates.
ko...@thomeer.be <ko...@thomeer.be> #11
I'm using the national ID card of Belgium. The site is http://eid.belgium.be . Since "--use-system-ssl" support has been removed, it doesn't work any more.
rs...@chromium.org <rs...@chromium.org> #12
@koen: Are you also on Windows?
ko...@thomeer.be <ko...@thomeer.be> #13
@rsleevi: Yes (Win7 32bit), Chrome: 26.0.1410.43 m
ju...@chromium.org <ju...@chromium.org> #14
[Empty comment from Monorail migration]
rs...@chromium.org <rs...@chromium.org> #15
The Belgium EID middleware source is available at https://code.google.com/p/eid-mw/source/browse
The relevant CSP hasn't been updated since 2010. A quick inspection of the CSP shows it supports the necessary CP* functions that Chrome expects onhttp://src.chromium.org/viewvc/chrome/trunk/src/net/third_party/nss/ssl/sslplatf.c?view=log#revHEAD
Namely, it supports CPGetUserKey (CryptGetUserKey), CPGetKeyParam (CryptGetKeyParam) with KP_ALGID, CPCreateHash, CPGetHashParam (with HP_HASHSIZE), CPSetHashParam (with HP_HASHVAL), and CPSignHash. So it's not immediately clear to me why it's failing.
Likely need to add more diagnostic capabilities, such as recording the OS error and/or additional logging. Alternatively, writing a sample tool for conformance tests.
I don't see myself being able to get this in the next two weeks, so marking it Available in case someone wants to take a stab at it.
The relevant CSP hasn't been updated since 2010. A quick inspection of the CSP shows it supports the necessary CP* functions that Chrome expects on
Namely, it supports CPGetUserKey (CryptGetUserKey), CPGetKeyParam (CryptGetKeyParam) with KP_ALGID, CPCreateHash, CPGetHashParam (with HP_HASHSIZE), CPSetHashParam (with HP_HASHVAL), and CPSignHash. So it's not immediately clear to me why it's failing.
Likely need to add more diagnostic capabilities, such as recording the OS error and/or additional logging. Alternatively, writing a sample tool for conformance tests.
I don't see myself being able to get this in the next two weeks, so marking it Available in case someone wants to take a stab at it.
rs...@chromium.org <rs...@chromium.org> #16
[Empty comment from Monorail migration]
me...@chromium.org <me...@chromium.org> #17
Hi Georgi, Rossen, et al.
I'm looking into this issue and it appears that at least in Clauer device case the problem is that it does not report correct algorithm in response to CPGetKeyParam with KP_ALGID.
Could you try attached test app (run from command line without parameters) and update the issue with the results?
thanks,
-m
I'm looking into this issue and it appears that at least in Clauer device case the problem is that it does not report correct algorithm in response to CPGetKeyParam with KP_ALGID.
Could you try attached test app (run from command line without parameters) and update the issue with the results?
thanks,
-m
we...@gmail.com <we...@gmail.com> #18
No Test Parameters, entering interactive mode
The store has been opened.
Got Cert:
Private Alg:1.2.840.113549.1.1.5
Public Alg:1.2.840.113549.1.1.1
Acquiring Private Key Context.
Acquired Context, Test Signing.
*** keyAlg is 0, default to CALG_RSA_SIGN
***Unknown Alg: 0
PORT_SetError:-8152, GetLastError()=0x00000000
PORT_SetError:-1, GetLastError()=0x00000000
Signature Test Failed!
The store has been opened.
Got Cert:
Private Alg:1.2.840.113549.1.1.5
Public Alg:1.2.840.113549.1.1.1
Acquiring Private Key Context.
Acquired Context, Test Signing.
*** keyAlg is 0, default to CALG_RSA_SIGN
***Unknown Alg: 0
PORT_SetError:-8152, GetLastError()=0x00000000
PORT_SetError:-1, GetLastError()=0x00000000
Signature Test Failed!
rs...@chromium.org <rs...@chromium.org> #19
[Empty comment from Monorail migration]
rs...@chromium.org <rs...@chromium.org> #20
Actually punting this one back to mef@. The Windows failures are unrelated to the client cert failures on other platforms.
ko...@thomeer.be <ko...@thomeer.be> #21
The issue with the Belgian eID (national ID card) has been resolved with the last middleware update.
https://code.google.com/p/eid-mw/downloads/list (7363b)
rs...@chromium.org <rs...@chromium.org> #22
[Empty comment from Monorail migration]
me...@chromium.org <me...@chromium.org> #23
@webdbase, thanks! This confirms my experiment and should be sufficient to produce the fix.
bu...@chromium.org <bu...@chromium.org> #24
------------------------------------------------------------------------
r195619 | mef@chromium.org | 2013-04-22T22:02:44.328205Z
Changed paths:
Mhttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/nss/nss/exports_win.def?r1=195619&r2=195618&pathrev=195619
- Added export of CERT_GetCertKeyType for ssl platform support
BUG=226455
Review URL:https://chromiumcodereview.appspot.com/14416002
------------------------------------------------------------------------
r195619 | mef@chromium.org | 2013-04-22T22:02:44.328205Z
Changed paths:
M
- Added export of CERT_GetCertKeyType for ssl platform support
BUG=226455
Review URL:
------------------------------------------------------------------------
bu...@chromium.org <bu...@chromium.org> #25
------------------------------------------------------------------------
r196010 | mef@chromium.org | 2013-04-24T02:38:51.778241Z
Changed paths:
Mhttp://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=196010&r2=196009&pathrev=196010
Update nss_revision to r195619 to pick up the export of CERT_GetCertKeyType from crnss
BUG=226455
The underlying CL ishttps://codereview.chromium.org/14416002/
R=wtc@chromium.org
TEST=no build errors on iOS, Mac OS X, and Windows.
Review URL:https://chromiumcodereview.appspot.com/14200046
------------------------------------------------------------------------
r196010 | mef@chromium.org | 2013-04-24T02:38:51.778241Z
Changed paths:
M
Update nss_revision to r195619 to pick up the export of CERT_GetCertKeyType from crnss
BUG=226455
The underlying CL is
R=wtc@chromium.org
TEST=no build errors on iOS, Mac OS X, and Windows.
Review URL:
------------------------------------------------------------------------
me...@chromium.org <me...@chromium.org> #26
[Empty comment from Monorail migration]
bu...@chromium.org <bu...@chromium.org> #27
------------------------------------------------------------------------
r196824 | mef@chromium.org | 2013-04-26T20:53:31.162431Z
Changed paths:
Mhttp://src.chromium.org/viewvc/chrome/trunk/src/net/third_party/nss/ssl/ssl3con.c?r1=196824&r2=196823&pathrev=196824
Mhttp://src.chromium.org/viewvc/chrome/trunk/src/net/third_party/nss/ssl/sslimpl.h?r1=196824&r2=196823&pathrev=196824
Mhttp://src.chromium.org/viewvc/chrome/trunk/src/net/third_party/nss/ssl/sslplatf.c?r1=196824&r2=196823&pathrev=196824
Use CERT_GetCertKeyType to get KeyType for ssl3_PlatformSignHashes.
This is based onhttps://crbug.com/chromium/14187006 , which was closed due to invalid Base URL.
BUG=226455
Review URL:https://chromiumcodereview.appspot.com/13843023
------------------------------------------------------------------------
r196824 | mef@chromium.org | 2013-04-26T20:53:31.162431Z
Changed paths:
M
M
M
Use CERT_GetCertKeyType to get KeyType for ssl3_PlatformSignHashes.
This is based on
BUG=226455
Review URL:
------------------------------------------------------------------------
me...@chromium.org <me...@chromium.org> #28
I've tried the fix on Windows XP with Clauer device.
de...@gmail.com <de...@gmail.com> #29
Hello,
I presume that this issue is fixed.
Where can I download the patch from?
This is urgent.
I presume that this issue is fixed.
Where can I download the patch from?
This is urgent.
me...@chromium.org <me...@chromium.org> #30
we...@gmail.com <we...@gmail.com> #31
That's great! I tried version 28.0.1500.11 dev-m with the Clauer device and it works!
me...@chromium.org <me...@chromium.org> #32
Excellent, thank you for testing!
is...@google.com <is...@google.com> #33
This issue was migrated from crbug.com/chromium/226455?no_tracker_redirect=1
[Monorail mergedwith:crbug.com/chromium/230760 ]
[Monorail components added to Component Tags custom field.]
[Monorail mergedwith:
[Monorail components added to Component Tags custom field.]
Description
Steps to reproduce the problem:
1. Browser started with:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --use-system-ssl
2. URL opened
3. Browser prompts for the certificate
4. Select the authentication certificate
5. Wait for the PIN 1 prompt.
What is the expected behavior?
Browser should prompt for PIN
What went wrong?
Грешка 141 (net::ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED): Неизвестна грешка.
Did this work before? Yes I'm not a frequent Chrome user but it surely worked with versions > 10
Chrome version: 26.0.1410.43 Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)