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

Replace Websockets with Quic (Xpra) #333

Open
MoritzWeber0 opened this issue Oct 16, 2024 · 2 comments
Open

Replace Websockets with Quic (Xpra) #333

MoritzWeber0 opened this issue Oct 16, 2024 · 2 comments
Labels
xpra Issues related to the Xpra remote connection method

Comments

@MoritzWeber0
Copy link
Member

Xpra-org/xpra-html5#143 (comment)

@MoritzWeber0 MoritzWeber0 added the xpra Issues related to the Xpra remote connection method label Oct 16, 2024
@zusorio
Copy link
Member

zusorio commented Oct 17, 2024

I looked into this a bit and I don't think it's feasible in our current state unfortunately. The main problems are:

  • No reverse proxies for WebTransport: It doesn't look like any widespread reverse proxies (Nginx, Caddy, Traefik) support proxying WebTransport. Our only option would be a raw UDP reverse proxy.
  • TLS Termination: WebTransport mandates using TLS all the way down to Xpra. This would mean that we would either have to re-encrypt traffic (which runs into the reverse proxy issue) or terminate TLS using Xpra (which would mean provisioning certs for every session container)

@MoritzWeber0
Copy link
Member Author

No reverse proxies for WebTransport: It doesn't look like any widespread reverse proxies (Nginx, Caddy, Traefik) support proxying WebTransport. Our only option would be a raw UDP reverse proxy.

This could be solved by directly exposing the port. But in the end the session container would need to handle authentication again and other features like session sharing etc. would be hard to implement.
But I guess there will be some reverse proxies for Quic in the future.

TLS Termination: WebTransport mandates using TLS all the way down to Xpra. This would mean that we would either have to re-encrypt traffic (which runs into the reverse proxy issue) or terminate TLS using Xpra (which would mean provisioning certs for every session container)

Yes, that's an annoying challenge and probably only feasible with wildcard certificates. Nothing for the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
xpra Issues related to the Xpra remote connection method
Projects
Development

No branches or pull requests

2 participants