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
feat(localip): use reserved remote address #4648
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll want to check this on my Windows and MacOS machines to make sure nothing breaks, but I think this is in pretty good form at the minute. A few small tweaks.
Instead of the remote address of 8.8.8.8 (Google DNS) in the crate local_ipaddress use a reserved IPv4 address, that should never be assigned. Also forward the underlying error on failure. Supersedes: starship#4614
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Thank you for your contribution @cgzones and thank you for reviewing @chipbuster. |
Instead of the remote address of 8.8.8.8 (Google DNS) in the crate local_ipaddress use a reserved IPv4 address, that should never be assigned. Also forward the underlying error on failure. Supersedes: starship#4614
Description
Instead of the remote address of 8.8.8.8 (Google DNS) in the crate
local_ipaddress
use a reserved IPv4 address, that should never be assigned.Also forward the underlying error on failure.
Motivation and Context
The current used crate
local_ipaddress
connects an UDP socket to 8.8.8.8 (Google DNS), which might trigger some privacy concerns (although no actual packet should be send).Supersedes: #4614
How Has This Been Tested?
Checklist: