Chrom[e | ium] 20 SSL problem

[primalmotion]

Hey,

With latest versions of Chromium, it is not possible to use SSL encrypted websocket.

When starting the proxy, this is thrown:

File "/tmp/work/archipel-agent-virtualmachine-vnc/archipelagentvirtualmachinevnc/websocket.py", line 723, in top_new_client
    self.client = self.do_handshake(startsock, address)
  File "/tmp/work/archipel-agent-virtualmachine-vnc/archipelagentvirtualmachinevnc/websocket.py", line 595, in do_handshake
    if wsh.last_code == 101:
AttributeError: WSRequestHandler instance has no attribute 'last_code'

By setting the cert to empty string, it works again, but with no encryption of course.

[kanaka]

It reproduced briefly for me. However, after re-accepting the self-signed cert (by using normal https to connect) and then reloading noVNC itself, the problem has now gone away. I think this is another symptom of the "no way to accept invalid certs over WebSockets" issue. Can you verify that forcing the cert to be accepted using https resolves the problem for you too?

[kanaka]

@primalmotion, ping.

[kidk]

I've come across this problem with noVNC. Accepting the cert trough https does indeed fix the problem.

[CyrilPeponnet]

I confirm this too, you can close this one I suppose. (Primalmotion can confirm also, we have discussed this case for archipel yesterday).

[kanaka]

Okay, thanks.