Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Support for Intel vPro KVM

Here you will find help for frequently asked questions as well as for your specific question
Post Reply
grubi
8
8
Posts: 23
Joined: 2012-01-14 21:03

Support for Intel vPro KVM

Post by grubi »

Hello.

Till last year it was possible to use UltraVNC successfully with the Intel vPro KVM feature (RFB password via Port 5900).
It seems that Intel has disabled support for this access method for security reasons and so we can no longer use UltraVNC for that.

https://software.intel.com/sites/manage ... t5900.htm

https://github.com/Ylianst/MeshCommander/issues/98

As it is still possible to access Intel KVM via MeshCommander I wanted to ask if there is still a way to use UltraVNC with updated Intel Firmware?

Seems that this user has developed a VNC shim layer in Python to make it still work

https://github.com/jsastriawan/pyws/blob/main/amtkvm.py

Thanks
grubi
8
8
Posts: 23
Joined: 2012-01-14 21:03

Re: Support for Intel vPro KVM

Post by grubi »

Some additional notes:

New Intel firmware only disables non-TLS port 5900 for VNC. TLS connections over port 16993 and 16995 still work.

What the smart guy writing the shim layer did to make it still work is the following:
If you want, you can create a VNC shim layer to allow VNC client like Tiger VNC to talk to AMT KVM. This shim layer basically handles AMT Websocket Digest Authentication and initial KVM negotiation before shuffling the RFB3.8 stream between AMT and VNC Viewer.
As Intel also abandoned the software MeshCommander to force their customers to use their cloud management software it would be a real USP if UltraVNC could still be used for Intel KVM.
Post Reply