On Mon, Nov 25, 2024 at 6:33 PM Javier Fernandez <jfernan...@igalia.com> wrote:
> Hi Domenic, > On 25/11/24 5:56, Domenic Denicola wrote: > > > > On Fri, Nov 22, 2024 at 7:46 PM Javier Fernandez <jfernan...@igalia.com> > wrote: > >> Contact emails jfernan...@igalia.com >> >> Explainer >> https://github.com/WICG/webcrypto-secure-curves/blob/main/explainer.md >> >> Specification https://wicg.github.io/webcrypto-secure-curves/#x25519 >> > > Has there been any attempt to merge this into the main Web Crypto > specification? It's best to avoid monkey patch specifications > <https://annevankesteren.nl/2014/02/monkey-patch>, and if this is indeed > implemented in two browsers, that merger should be relatively easy. > > > > Yes, there is a PR [1] that has been approved by Mozilla and Apple, and we > are waiting for someone from Chrome to follow. It was also discussed in a > WebAppSec WG meeting 2 months ago, when some issues were identified; those > were already addressed, so I believe it's ready to be merged. > > [1] https://github.com/w3c/webcrypto/pull/362 > Awesome, thank you! +David Benjamin <david...@chromium.org>, do you have any concerns about whether the spec PR is at a sufficient level of detail to achieve interoperability? It seems like it's gone through a good amount of review to me, so I'm inclined to approve as an API owner, but if you have time to chime in that would be helpful to confirm. Javier, can you speak to whether there's web platform test coverage for the tricky issues that were discussed on the PR, e.g. the three listed in your last comment? -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra8qEyQ4UZjpNk20bjrDVcr_gWAuViFdNDXjqPR5S-AgyQ%40mail.gmail.com.
