Summary: | Inoperable remember ssl client certificate choice function in Gecko-based browsers | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey S. Starikoff <Ikonta> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED OBSOLETE | ||
Severity: | minor | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugzilla.mozilla.org/show_bug.cgi?id=523336 https://bugzilla.mozilla.org/show_bug.cgi?id=634697 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey S. Starikoff
2011-09-08 07:30:33 UTC
Please retry with Icecat-9.0, and nss-3.13.1-r2 and get back to us, thanks! Gone away with issued versions of IceCat. But remember client certificate choice function still inoperate in parent www-client/firefox-17.0.2 browser. Icecat was removed many moons ago. (In reply to comment #3) > Icecat was removed many moons ago. Looking on https://bugs.gentoo.org/show_bug.cgi?id=427186#c6 I think it is not right. The reported issue realates far not only GNU Icecat, but Gecko. On current stable www-client/firefox (17.0.4) I see exactly the same issue: memory client certificate choice function present, but don't works. If necessary, I cat make a check with www-client/seamonkey. (In reply to Sergey S. Starikoff from comment #4) > (In reply to comment #3) > > Icecat was removed many moons ago. > > Looking on https://bugs.gentoo.org/show_bug.cgi?id=427186#c6 I think it is > not right. > > > The reported issue realates far not only GNU Icecat, but Gecko. > > On current stable www-client/firefox (17.0.4) I see exactly the same issue: > memory client certificate choice function present, but don't works. > > If necessary, I cat make a check with www-client/seamonkey. Can you still duplicate your results using latest stable and a clean profile? (In reply to Jory A. Pratt from comment #5) > Can you still duplicate your results using latest stable and a clean profile? On =www-client/firefox-17.0.7 (amd64 build) with clean profile on production web resource issue was reproduced. (In reply to Sergey S. Starikoff from comment #6) > (In reply to Jory A. Pratt from comment #5) > > Can you still duplicate your results using latest stable and a clean profile? > > On =www-client/firefox-17.0.7 (amd64 build) with clean profile on production > web resource issue was reproduced. I am still unable to reproduce this with thunderbird-31.3.0 If you can provide me with a better way to reproduce I would like to get this closed. (In reply to Jory A. Pratt from comment #7) > I am still unable to reproduce this with thunderbird-31.3.0 If you can > provide me with a better way to reproduce I would like to get this closed. =www-client/firefox-31.5.3 — issue still present. Another upstream bug, describing similiar issue, was confirmed: https://bugzilla.mozilla.org/show_bug.cgi?id=634697 Last user's comment: (In reply to Tim Berners-Lee from comment #11) > I have been annoyed by this problem for years, mentioned in in talks, > discussed it with Anne van K in the TAG, and general taken it as indicating > a lack of interest at Mozilla in client-side certs. (Chrome does not have > this problem, and so is easier to use if you use client certs a lot.) At > least from the discussion here it seems to be recognized as bug -- but has > a status of "UNCONFIRMED" surprises me. So maybe it difficult to reproduce. > If it is supposed to work, where is the site->cert mapping stored? And developer's answer: (In reply to David Keeler [:keeler] (use needinfo?) from comment #12) > For what it's worth, I can reproduce the bug. You're right that client-side > certificate-related features aren't a high priority right now, since the > majority of our users don't use them. It's unfortunate, but limited > engineering resources mean we can't address everything we might want to. I've generate the certificate set for localhost server to reproduce this issue. If anybody is interested in it (and it can help them to work on this issue), I can attach that files. If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team |