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

RFE: TLS API #385

Closed
CendioOssman opened this issue Dec 9, 2024 · 2 comments
Closed

RFE: TLS API #385

CendioOssman opened this issue Dec 9, 2024 · 2 comments

Comments

@CendioOssman
Copy link

We at noVNC have a bit of an odd request, in that we'd like access to the browsers complete TLS implementation from JavaScript. Not just the crypto routines, but also the protocol handling.

The use case is that we are handling a non HTTP protocol entirely from JavaScript, tunnelled via some intermediary. That means that the TLS protecting the HTTP transport might just be one hop, and TLS is desired to protect the entire chain.

We don't want to develop and maintain our own TLS implementation entirely in JavaScript. As a result, we currently have to tell users to disable TLS between the HTTP proxy and VNC server.

@twiss
Copy link
Member

twiss commented Dec 10, 2024

Hi 👋 I think this is a bit out of scope for Web Crypto, and might need to be brought to the WICG.

P.S. there is already a JS implementation of TLS, here: https://github.com/digitalbazaar/forge.

@twiss twiss closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2024
@CendioOssman
Copy link
Author

Hi 👋 I think this is a bit out of scope for Web Crypto, and might need to be brought to the WICG.

I've filed a proposal here now: WICG/proposals#192

P.S. there is already a JS implementation of TLS, here: https://github.com/digitalbazaar/forge.

It's something we've considered, but I don't think that gives me the same confidence as getting access to NSS or OpenSSL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants