New issue
Advanced search Search tips

Issue 614385 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
davidben@chromium.org
agl@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocking:
issue 394945



Sign in to add a comment

Move WebCrypto implementation into Blink

Project Member Reported by eroman@chromium.org, May 24 2016 
WebCrypto is currently split between:

  //third_party/WebKit/Source/modules/crypto/
  ///components/webcrypto
  //third_party/WebKit/public/platform

The actual cryptographic implementation (which is solely BoringSSL now) lives in the Chromium side, whereas the Javascript/DOM interfacing is all on the Blink side. Some features like JWK straddle both ends.

It would make sense now to merge the actual cryptographic implementation into Blink and simplify the code.

It should be a net win, especially the code for JWK, and WebWorkers. (Unfortunately the algorithm normalization may need to continue to be exposed as a public interface because it is used by enterprise platformKeys extension, so not everything can be simplified right away).

One of the main dependencies that will need to be figured out is //src/crypto. The components/webcrypto code currently uses the scoped OpenSSL helpers from that extensively, (but not much else).

Comment 1 by davidben@chromium.org, May 24 2016

Cc: agl@chromium.org
+agl, what do you think about putting OpenSSL scopers in BoringSSL? We seem to keep writing different versions of them everywhere, even within our own tests, and now that std::unique_ptr is available everywhere, we should be able to freely use it in our scopers.

Comment 2 by agl@chromium.org, May 24 2016 

R.e. #1: I think that would be a great idea.

Comment 3 by eroman@chromium.org, Jul 14 2016

Blocking: 394945

Comment 4 by eroman@chromium.org, Jul 14 2016

Labels: -Type-Bug Type-Feature
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 17 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by eroman@chromium.org, Jul 20 2017

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 23

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by eroman@chromium.org, Jul 31

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
►

Sign in to add a comment