MS-RDPBCGR: Virtual Channel PDU transmission¶
Microsoft. (2026). MS-RDPBCGR: Virtual Channel PDU transmission: Virtual Channel PDU transmission.
Cited by¶
8 citations across 1 artifact.
Domain-specific¶
- Authenticated multiplexed remote-service session
- The streams can serve different operations while sharing the successful security and session setup; their identification keeps data and requests directed to the proper service.
- In the selected RDP case, the client accepts the intended listener certificate, CredSSP binds authentication to TLS, and later Direct Approach traffic remains externally protected.
- The streams can serve different operations while sharing the successful security and session setup; their identification keeps data and requests directed to the proper service.
- RDP static channels are requested options, not a property of every connection; CredSSP also permits a certificate without a commonly trusted CA root, so a certificate's presence cannot stand in for acceptance of the intended server.
- The streams can serve different operations while sharing the successful security and session setup; their identification keeps data and requests directed to the proper service.
- RDP assigns channel IDs to core I/O and requested static channels; a receiver verifies or decrypts a virtual-channel PDU before routing its payload by that ID.
- In the selected RDP sequence, channel joins precede remote user authorization; denial closes the connection, while completed authorization and finalization precede desktop and clipboard payload.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 8 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 7 other ways.
- https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/023f1e69-cfe8-4ee6-9ee0-7e759fb4e4ee ×1
- https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/26043070-85f8-4ee8-8721-d7f013c755ca ×1
- https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/334495b7-47b9-4e91-8d08-05d46285799b ×1
- https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/343e4888-4c48-4054-b0e3-4e0762d1993c ×1
- https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/8e11581d-094f-461a-9fde-ba51af90cf8b ×1
- https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/a547e3da-4526-43e8-85c6-ec9dba584907 ×1
- https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/b2bd18fa-0066-4a57-ac25-9139c0df31e0 ×1
Registry ID ref:69ae41a67e63 · see in the full table