Closed Bug 1564509 Opened 6 years ago Closed 6 years ago

Remove support for DH from WebCrypto API (not in spec)

Categories

(Core :: DOM: Web Crypto, task, P1)

task

Tracking

()

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: jcj, Assigned: jcj)

References

Details

(Keywords: site-compat)

Attachments

(1 file)

Bug 1034856 added support for DH algorithms to WebCrypto, however the final specification did not choose to include them, making Firefox the only browser with support.

Bug 1539578 added telemetry to show usage, and it is extremely low (not appearing on the graphs), which could be expected as Firefox is the only supporting browser.

Since DH is an ongoing maintenance burden -- and overall cryptanalysis of DH is progressing -- let's remove it.

Keywords: site-compat

Bug 1034856 added support for DH algorithms to WebCrypto, however the final
specification did not choose to include them, making Firefox the only browser
with support.

Bug 1539578 added telemetry to show usage, and it is extremely low (not
appearing on the graphs), which could be expected as Firefox is the only
supporting browser.

Since DH is an ongoing maintenance burden -- and overall cryptanalysis of DH
is progressing -- let's remove it.

Notice to unship went to dev-platform on 29 March 2019 with no objections. [0]

[0] https://groups.google.com/d/msg/mozilla.dev.platform/Ut3-eQmUdWg/O9w1et1aBgAJ

Pushed by jjones@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5d93cdf79d27 Remove DH from WebCrypto r=kjacobs,bzbarsky,keeler
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72

Posted a site compatibility note for this.

Should this have been uplifted to the ESR, especially given:

https://blog.intothesymmetry.com/2020/01/the-curious-case-of-webcrypto-diffie.html

I don't believe this warrants an uplift to ESR; one would have to go out of their way to build a WebCrypto application using FFDH, and then have that application be vulnerable to XSS. The full discussion of that is in Bug 1471684, which will likely be unhidden shortly.

Blocks: 1471684
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: