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.

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

GUACAMOLE-1020: Perform some additional null checks in restriction verification service. #1022

Merged

Conversation

necouchman
Copy link
Contributor

I've added a few null checks and re-arranged a couple of other checks to address some issues that Coverity flagged in the recently-committed login restriction code.

Copy link
Contributor

@mike-jumper mike-jumper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking these changes, I'm not sure where Coverity saw the potential for null values. Could these be all false positives?

@necouchman
Copy link
Contributor Author

Looking these changes, I'm not sure where Coverity saw the potential for null values. Could these be all false positives?

They seemed a little false-positive to me, but who am I to question Coverity?!

@necouchman
Copy link
Contributor Author

Looking these changes, I'm not sure where Coverity saw the potential for null values. Could these be all false positives?

Okay, I've removed all of the additional null checks that I put in there, and stuck with two changes - the first is to move the creation of the HostName object to after the null check for the remoteAddress string, which I still think makes sense. Other than that, just a couple of code readability clean-ups.

@mike-jumper mike-jumper merged commit 776be04 into apache:staging/1.6.0 Oct 4, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants