Fix for issue 105 -- more robust IP and hostname validation #107
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.
Added a regex to look for hostname and IPV4 patterns. If this first check passes, then the
ipaddress
module from the standard library is used to validate the IP address. If a hostname is detected instead of an IP address, it will try to get the fully qualified domain name. Keeping within the standard library,socket.getfqdn
was used for this step. Let me know if you think the FQDN part might be overkill.I added this for options 1 and 7, which prompt the user for an IP address or domain. I left out the domain part for option 7.
Edit to remove stale tag.