Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34516 - [chromium] Certificate-based client authentication doesn't work

Attached to Project: Arch Linux
Opened by akulikov (akulikov) - Friday, 29 March 2013, 12:26 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 07 May 2013, 22:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
https://code.google.com/p/chromium/issues/detail?id=224897

Connection to the server is using 128 bit encryption and using TLS 1.0.
For message authentication using RC4_128 with MD5.
Key exchange using RSA.
Connection does not use SSL compression


Additional info:
* package version(s)
26.0.1410.43-2
* config and/or log files etc.
http://pastebin.com/ZFqRiSVj

Steps to reproduce:
1. open a site that requires a client certificate (issued by the Win2k CS for IIS 6)
2. agree with the fact that the server certificate is self-signed
3. select a certificate instead of a window get an error 403.7
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Tuesday, 07 May 2013, 22:53 GMT
Reason for closing:  Deferred
Additional comments about closing:  Chromium 28 should include this fix.
Comment by akulikov (akulikov) - Friday, 12 April 2013, 07:27 GMT
Can I help more than that?
In new build (26.0.1410.63-1) problem still happens
Comment by Evangelos Foutras (foutrelis) - Friday, 12 April 2013, 12:30 GMT
You can test google-chrome¹ — if it exhibits the same behavior then it's most likely an upstream issue.

¹ https://aur.archlinux.org/packages/google-chrome/
Comment by akulikov (akulikov) - Friday, 12 April 2013, 22:28 GMT
Yep, i'm test in google-chrome from aur and issue reproduced in it.
Comment by akulikov (akulikov) - Friday, 12 April 2013, 22:30 GMT
How to be on? For me, this issue is very critical, because I very often work with client certificates.
Comment by Evangelos Foutras (foutrelis) - Saturday, 13 April 2013, 12:23 GMT
Have you imported your client certificate into Chromium?

https://antportal.com/wiki/installing_client_certificates/
Comment by akulikov (akulikov) - Monday, 15 April 2013, 06:15 GMT
Yes, I imported my client certificates into Chromium (and into Chrome at the time of testing). I also tried to delete the imported certificates and import them again. All the certificates were issued by Windows 2003 Server. If I rolling back to version of Chromium 25 - all works. Therefore, most likely, there is a problem in version 26.
Comment by akulikov (akulikov) - Monday, 15 April 2013, 06:27 GMT
http://prntscr.com/10opbg
http://prntscr.com/10opd8
http://prntscr.com/10oplm
http://prntscr.com/10opn4
Comment by Evangelos Foutras (foutrelis) - Monday, 29 April 2013, 08:07 GMT
Looks like upstream has committed a fix for this issue; unless they also backport it, we'll have to wait until Chromium 28 for this be solved.
Comment by akulikov (akulikov) - Monday, 29 April 2013, 12:20 GMT
thanks for help!

Loading...