Add initial auth support for AST2400 based boards

[devicenull]

Supermicro X11SSE-F boards use an entirely different auth scheme from the previous ones (but yes, they've hijacked auth type 16 again...).

Luckily, they present a server version of 055.008, so they're pretty easy to detect.

Another change with these controllers, is you have to use websockify's --tls-client flag. The IPMI controller now speaks VNC over SSL.

While this will successfully auth, it will not remain connected and actually work. We end up disconnecting with 'Unexpected server message (Type: 66)', but it's a start.

[disaster123]

Another note this ALSO applies to X10 boards with redfish support.

[LAKostis]

@DisasteR I'd rather disagree, we have 2 different X10 w/ latest fw and both variants (REDFISH and SMT_X10) work well with my patch.

…

On Fri, 24 Mar 2017 at 22:05, disaster123 ***@***.***> wrote: Another note this ALSO applies to X10 boards with redfish support. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJhvQWYAtIvmuvdXCbA-Zh9vzzzpnSqpks5rpDAOgaJpZM4Movh2> .

[devicenull]

We also have a bunch of X10 boards that have been working well without this. It comes down to the IPMI controller, if you have an X10 with Aspeed AST2400, then it would probably have issues.

I also have more of the protocol working and can see video... but the keyboard input drops the connection (and breaks the KVM until you do the iKVM reset)

[disaster123]

@LAKostis i don't know hwta oyu want to tell me. I have never told that all X10 boards are affected but there are X10 board which have the same problems like X11 / AST2400 chip.

[LAKostis]

@disaster123 I was just curious about because you've mentioned about existing problems with REDFISH_ firmwares for X10 but again we never had any troubles with them. Maybe it's another surprise from Supermicro where they activate different functionality within the same image.

[devicenull]

Added support for actually sending keyboard/mouse events. These are helpfully exactly the same as the ATEN ones.

This is largely functional at this point; though for some reason caps lock isn't working and the video display gets laggy if you move the mouse around a lot.

[psyno]

I wanted to try your changes for AST2400 but i already failed with websockify. Tried to pass "--ssl-target" or "--ssl-only" but all i get is:

handler exception: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:581)

Any hints?

[maisn3r]

Hello all,

i also have problem AST2400, my server boards are X10DRL-i with AST2400, trying from 3 days to bring noVNC to works with this stupid things without success. I have also few IDRAC8 servers which using standard VNC protocol and working like a charm, really need somebody help, i am happy to pay for the work!

[maisn3r]

Hello,

i have success with that video, you need stunnel as client after the websockify, also got che client certs and keys from the java application, now working perfect. The problem is X11SSL-f not working on this ways i am afraid, searching UDP port 623 also.