MDMServer: handling of invalid port in mDNS response #479
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
saauvine
approved these changes
Oct 1, 2024
joenpera
approved these changes
Oct 1, 2024
saauvine
reviewed
Oct 1, 2024
modules/sc-mesh-secure-deployment/src/nats/src/comms_service_discovery.py
Outdated
Show resolved
Hide resolved
saauvine
requested changes
Oct 1, 2024
johan-juntunen
force-pushed
the
mdm-agent-check-mdm-server-port
branch
from
dc92a93 to
1d9d9de
Compare
…tening for mDNS responses -SECO-7799
johan-juntunen
force-pushed
the
mdm-agent-check-mdm-server-port
branch
from
1d9d9de to
f34c78c
Compare
saauvine
approved these changes
Oct 1, 2024
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.
If MDMServer port in mDNS response is None, keep listening for mDNS responses
-SECO-7799