New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: AES-KW through main process Web Crypto API causes SIGABRT #36256
Comments
quick question: how come Bun (also uses BoringSSL) has support of AES Key Wrap and yet the electron main process doesn't support it, while the renderer process does (fiddle gist)... |
@panva that'd be because in the renderer process, you have access to WebCrypto APIs provided by Chromium/Blink, whereas in the main process they're backed by Node.js. I can look into what options we might have. |
I get that but its still boringssl backing both, isnt it? |
yeah - and it does look like it's available in BoringSSL here. Lemme dig into it some more. FWIW bun seems to roll it all themselves: https://github.com/oven-sh/bun/tree/6142715c06d5eb3dbaa07901a6281ae1394483a9/src/bun.js/bindings/webcrypto |
Refs: electron/electron#36256 PR-URL: #45321 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Shelley Vohr <shelley.vohr@gmail.com>
Refs: electron/electron#36256 PR-URL: nodejs#45321 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Shelley Vohr <shelley.vohr@gmail.com>
Refs: electron/electron#36256 PR-URL: #45321 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Shelley Vohr <shelley.vohr@gmail.com>
Refs: electron/electron#36256 PR-URL: #45321 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Shelley Vohr <shelley.vohr@gmail.com>
Refs: electron/electron#36256 PR-URL: #45321 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Shelley Vohr <shelley.vohr@gmail.com>
Refs: electron/electron#36256 PR-URL: #45321 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Shelley Vohr <shelley.vohr@gmail.com>
Refs: electron/electron#36256 PR-URL: #45321 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Shelley Vohr <shelley.vohr@gmail.com>
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
@codebytere aside of the crash that will get fixed when the mentioned node PR makes it to a release electron includes, did you have a chance to see if AES-KW is not available intentionally or if it maybe could be enabled? |
@panva the crash has since been resolved, and i haven't had time yet but i still plan to look into potentially enabling it! |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue. |
Preflight Checklist
Electron Version
21.2.2
What operating system are you using?
macOS
Operating System Version
Ventura
What arch are you using?
arm64 (including Apple Silicon)
Last Known Working Electron version
n/a
Expected Behavior
I would expect the wrapKey call to be rejected instead of SIGABRT on the account of AES-WRAP not being supported in BoringSSL.
Actual Behavior
Testcase Gist URL
https://gist.github.com/0a69f62d5d1257956d9556a7451889b5
Additional Information
No response
The text was updated successfully, but these errors were encountered: