[Webkit-unassigned] [Bug 129928] New: WebCrypto should be available in workers

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=129928

           Summary: WebCrypto should be available in workers
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ap at webkit.org
                CC: syoichi at outlook.com
            Blocks: 122679



Syoichi Tsuyuhara <syoichi at outlook.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |syoichi at outlook.com


SubtleCrypto algorithms just got exposed on workers.

Probably the most notable part of work here is to make structured clone work with CryptoKeys in workers.

Also from the WG resolution:

---------------------------
The previous blocking issues were:
1) Should we define sync interfaces
2) How do we handle multi-threaded Key access

We resolved point 1 by saying "No"
  - In the future, if we wish to do so, it can be as part of / extension to the Promise interface" (eg: imagine a promise.wait() method)
We resolved point 2 by removing the Key Storage (long ago), allowing Keys to be handled in IDB. 
  - All cryptographic state is handled within the Promise, which isn't transferrable between workers
  - Key tainting is no longer required, by virtue of moving the hashed attributes into key generation, so we don't have synchronization risks there
  - Regardless, by virtue of the Promises() interface, implementations can take their own approach to scheduling the work for promises
---------------------------

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.