VirtualBox

Opened 13 years ago

Closed 13 years ago

#8032 closed defect (fixed)

Protocol violation: PDUTYPE2_SYNCHRONIZE, versionLow MUST be 1 but is 0

Reported by: kiilerix Owned by:
Component: RDP Version: VirtualBox 4.0.0
Keywords: Cc:
Guest type: other Host type: other

Description

VirtualBox will occasionally send (keep-alive?) packages with a (decrypted) content of

16 00 07 00 00 00 00 00 00 00 00 00 04 00 1f 00 00 00 00 00 00 00

where 7 = PDUTYPE_DATAPDU, versionLow = 0, versionHigh = 0, uncompressedlength = 4, streamid = 0, 1f = PDUTYPE2_SYNCHRONIZE, and messageType = 0.

BUT http://msdn.microsoft.com/en-us/library/cc240576 says that versionLow "MUST be set to TS_PROTOCOL_VERSION (0x1)", and the 3rd byte should thus have been 17.

AND messageType in TS_SYNCHRONIZE_PDU is 0 despite http://msdn.microsoft.com/en-us/library/cc240490 says "This field MUST be set to SYNCMSGTYPE_SYNC (1)."

It seems like it isn't a SYNCHRONIZE at all, but AFAICS it can't be anything else.

("All" other similar packages before this are fine - I do for example see another synchronize package as:

16 00 17 00 00 00 00 00 00 00 00 01 16 00 1f 00 00 00 01 00 00 00 )

This violation of the specification prevents interoperability with more standard compliant clients.

VirtualBox-4.0-4.0.0_69151_fedora14-1.i686 Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack

Change History (2)

comment:1 by sunlover, 13 years ago

Will be fixed in next VBox release.

The packet is indeed sent as a keep alive message.

comment:2 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

Fixed since VBox 4.0.2.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use