Pierre Ossman (ThinLinc team)

No response, closing.

Apparently browsers have got relative URL support for WebSockets now: https://github.com/whatwg/websockets/issues/20 We still need to support older browsers, though, and for historical reasons we don't have a simple URL interface...

A more general fix has been committed as 96c76f7709037956e760ae5f58dbde1bc1308bba. I still want to thank you for your efforts in getting this resolved, @vsilvar.

Looks nice and clean, so a good start. But if browser support is too poor then I don't think we want to merge it yet. I'm not sure how paste...

What I'd like to see broad support in the browsers. I.e. this works on at least Chrome, Firefox and Safari (Edge would be nice too though). Failing that, a clean...

Maybe I'm missing something, but if I understand you correctly, websockify crashes if you try to combine wrapping with a unix socket target? That seems like a bug we should...

Looking at the code, it looks like it will read the certificate on each connection. So you should be able to just replace the certificate file. Have you tried that...

Seems reasonable. Please send this as a pull request and we can look at the details.

Perhaps rather than wholesale switching between PC/SC implementation, it could be possible to aggregate them? Something similar to how p11kit. Different PC/SC providers would register themselves globally in the system,...

It's probably not very common, but I can think of two scenarios: * Remote access to an otherwise local session. Depending on your security model, you might want to retain...