Add basic support for parsing Dynamic Channels (drdynvc) #232
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Res260
changed the title
|
Damn, I screwed up... Edit: Phew! I managed to revert all that. |
obilodeau
force-pushed
the
dynamic_channels
branch
from
fa5f437
to
c134518
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on a CTF challenge, I wanted to test some things with the dynamic channels (if you come across this PR in the context of said CTF, this PR will NOT help you solve the challenge), so I built a basic MITM object to interact with them.
For reference, dynamic channels ( https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpedyc/3bd53020-9b64-4c9a-97fc-90a79e7e1e06 ) is the "new and improved" way to extend RDP functions
Some examples of channels that were opened using win10 mstsc to another win10 machine:
I'll leave this PR as a WIP because it has not been tested enough to go to production and the current logs do not bring a lot of values. However, if we ever plan to implement a sub-MITM for a specific dynamic channel, this might come in handy!