Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Recognize UltraVnc and TightVNC server by security type #506

Merged
merged 2 commits into from
Mar 16, 2022
Merged

Recognize UltraVnc and TightVNC server by security type #506

merged 2 commits into from
Mar 16, 2022

Conversation

badda71
Copy link
Contributor

@badda71 badda71 commented Mar 15, 2022 •
edited

Closes #505

@badda71 badda71 mentioned this pull request Mar 15, 2022
Closed
bk138
bk138 requested changes Mar 15, 2022
View reviewed changes
libvncclient/rfbproto.c Show resolved Hide resolved
libvncclient/rfbproto.c Outdated Show resolved Hide resolved
@bk138 bk138 merged commit a04fed5 into LibVNC:master Mar 16, 2022
@bk138
Copy link
Member

bk138 commented Mar 16, 2022

Looks good, thanks for the contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bk138 bk138 bk138 requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

DefaultSupportedMessagesUltraVNC() and DefaultSupportedMessagesTightVNC() are never called
2 participants
@badda71 @bk138