dustinac - 2012-12-23

A prerequisite for this to get integrated will be good documentation of how the protocol works, since I'm neither capable nor interested in reverse engineering it. Even better would be a working patch. Another thing is that compatibility with this KVM can't cause any new compatibility problems with existing servers. Hopefully they're using their own proprietary code numbers at some point to signal their extensions, but some other unambiguous method of detection would also be okay.

One observation I'll make is that Tight authentication is not so much an authentication method so much as a way of activating a number of Tight-specific extensions. It might be using that as a way to signal its own proprietary extensions.