RDP/settings: avoid divide-by-zero when optimal client resolution is unavailable#681
RDP/settings: avoid divide-by-zero when optimal client resolution is unavailable#681chrilep wants to merge 1 commit into
Conversation
|
I understand why the project wants things like a contributor agreement, but the other patch is critical our use of Are you just going to ignore these issues? We're considering recreating the patches and going through the submission process, but that raises questions about possible copyright violations of the originals. |
|
@clhedrick We do not require contributor agreements in order to accept pull requests. All that's required is:
As far as "ignoring these issues" - I wouldn't say we're ignoring them, but we do require that those who submit the pull requests be willing to work through the above process in order to accept the changes. Occasionally we will take an in-progress pull request, pull in the commits from the request, and finish out the changes. However, that's less common than trying to get people who are interested in the changes to participate in and contribute to the project. |
Summary
This PR prevents a divide-by-zero in
guac_rdp_parse_args()when client handshake data does not provide a validoptimal_resolution.Problem
settings->widthandsettings->heightwere derived using:... / user->info.optimal_resolutionIf
optimal_resolutionis0, this can trigger SIGFPE.Change
if (user->info.optimal_resolution > 0)RDP_DEFAULT_WIDTH,RDP_DEFAULT_HEIGHT) otherwiseBehavior
optimal_resolutionScope
Focused bugfix only; no protocol or feature changes.
AI Assistance Disclosure
Parts of this contribution (analysis and code drafting) were created with assistance from GitHub Copilot (GPT-5.3-Codex) and then reviewed/refined before submission.