-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[core,caps] Allow invalid TS_GENERAL_CAPABILITYSET::protocolVersion #10202
Conversation
some FreeRDP versions did send an invalid value of 0x0000 instead of the required 0x200. Log this kind of violation but continue.
clang-tidy review says "All clean, LGTM! 👍" |
Refer to this link for build results (access rights to CI server needed): |
@freerdp-bot test |
@freerdp-bot test again please |
Refer to this link for build results (access rights to CI server needed): |
@freerdp-bot test please |
Refer to this link for build results (access rights to CI server needed): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok for me, in rdp_write_general_capability_set
we should also ignore the value from the settings and always send TS_CAPS_PROTOCOLVERSION
.
@freerdp-bot test |
Refer to this link for build results (access rights to CI server needed): |
I guess that at end that what we will do. But in the meantime that would prevent behaviors like in proxies where you have front settings that you copy as is for the back connection. And so if an old FreeRDP connects front you will fail to connect back because of the check in the write function. Another possibility is to not store the value in the settings when reading the capability set... |
@freerdp-bot test please |
Refer to this link for build results (access rights to CI server needed): |
@freerdp-bot test please |
Refer to this link for build results (access rights to CI server needed): |
@freerdp-bot test please |
Refer to this link for build results (access rights to CI server needed): |
some FreeRDP versions did send an invalid value of 0x0000 instead of the required 0x200. Log this kind of violation but continue.