RESOLVED WONTFIX60232
Associate <keygen> request with Frame.
https://bugs.webkit.org/show_bug.cgi?id=60232
Summary Associate <keygen> request with Frame.
Matt Mueller
Reported 2011-05-04 17:42:04 PDT
In Chromium Linux we have to be able to show a dialog to unlock crypto devices when doing a keygen. We'd like this to be a tab-constrained dialog instead of a regular one. This change allows associating a specific keygen request with the tab that caused it.
Attachments
patch (18.10 KB, patch)
2011-05-04 17:46 PDT, Matt Mueller
abarth: review-
Matt Mueller
Comment 1 2011-05-04 17:46:17 PDT
Matt Mueller
Comment 2 2011-05-04 17:58:08 PDT
The chromium side changes are: http://codereview.chromium.org/6928021/ (needs to be landed first) and http://codereview.chromium.org/6930029/ (can be landed once this the webkit change is landed)
Adam Barth
Comment 3 2011-05-04 18:00:37 PDT
Comment on attachment 92350 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=92350&action=review > Source/WebCore/platform/android/SSLKeyGeneratorAndroid.cpp:29 > +#include "Document.h" The platform directory cannot include files from WebCore that are outside the platform directory. Your root problem is that you need to go "up" to the client, not down to the platform, to solve this problem.
Alexey Proskuryakov
Comment 4 2011-05-05 11:24:26 PDT
> In Chromium Linux we have to be able to show a dialog to unlock crypto devices when doing a keygen I'm curious what this dialog is about. Does it need to be displayed before any call to WTF::cryptographicallyRandomNumber()?
Adam Barth
Comment 5 2011-05-05 11:29:15 PDT
> I'm curious what this dialog is about. Does it need to be displayed before any call to WTF::cryptographicallyRandomNumber()? I'm not entirely sure, but I think "crypto devices" means something like a smart card.
Matt Mueller
Comment 6 2011-05-05 13:58:08 PDT
Yes, this is about unlocking a smart card or password-protected software security device before doing the keygen.
Ryosuke Niwa
Comment 7 2019-08-16 17:21:27 PDT
We should just remove this element: https://bugs.webkit.org/show_bug.cgi?id=167018
Note You need to log in before you can comment on or make changes to this bug.