crabapples
/
noVNC
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added support for RealVNC 5.3: RFB max version is 3.8, but RealVNC 5.3 sends "005.000" as the version string since they've extended their implementation upon RFB v3.8. Since RealVNC 5.3 implementss RFB v3.8 the noVNC client can interpret the "005.000" version string as RFB v3.8. The patch is tested against a fresh install of RealVNC Server 5.3 running on Windows 7 x64.

This commit is contained in:
Lars Ole Hurlen 2016-03-11 08:32:50 +01:00
parent b403cb92fb
commit 5157d32077
2 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
include/rfb.js
View File

@ -645,6 +645,7 @@ var RFB;
case "003.008":
case "004.000": // Intel AMT KVM
case "004.001": // RealVNC 4.6
case "005.000": // RealVNC 5.3
this._rfb_version = 3.8;
break;
default:

5
tests/test.rfb.js
View File

@ -545,6 +545,11 @@ describe('Remote Frame Buffer Protocol Client', function() {
expect(client._rfb_version).to.equal(3.8);
});
it('should interpret version 005.000 as version 3.8', function () {
send_ver('005.000', client);
expect(client._rfb_version).to.equal(3.8);
});
it('should fail on an invalid version', function () {
send_ver('002.000', client);
expect(client._rfb_state).to.equal('failed');