Skip to content
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

Switch from node-forge to a more robust TLS library #120

Open
alexhorn opened this issue Mar 14, 2022 · 1 comment
Open

Switch from node-forge to a more robust TLS library #120

alexhorn opened this issue Mar 14, 2022 · 1 comment
Assignees
Labels
code-quality Improving readability, maintainability or code robustness

Comments

@alexhorn
Copy link
Member

We should consider switching from our node-forge TLS/HTTP implementation to a more robust and established TLS library. For example, we could compile OpenSSL or mbedTLS to WASM.

Possibly useful projects:

@alexhorn alexhorn added the code-quality Improving readability, maintainability or code robustness label Mar 14, 2022
@M4GNV5
Copy link
Member

M4GNV5 commented Mar 14, 2022

The openssl wasm binary is 1.87MB.
The mbedtls one is very small but seems to be only used for elliptic curve crypto, it might get larger when exporting TLS functions.

As working with C WASM libraries is a pain and building cool WASM libs with Rust is super easy another option would be to use rustls which seems to not officially support WASM yet, but the newest comments sound like it could work.

@BuildmodeOne BuildmodeOne removed their assignment Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-quality Improving readability, maintainability or code robustness
Projects
None yet
Development

No branches or pull requests

3 participants