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

Bind to Only Loopback Address(es) When Making Interactive Request #797

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

crimsonvspurple
Copy link
Contributor

@crimsonvspurple crimsonvspurple commented Mar 11, 2024

Currently, we are creating Socket using InetSocketAddress(port) which is using wildcard address, so it will attempt to bind to all available network interfaces that includes private IP like 192.168.x.x, 10.x.x.x, etc; which in turns, may/will trigger the firewall prompt.

In this commit, we explicitly bind to loopback addresses only which will not trigger firewall.

…g InetSocketAddress(port) which is using wildcard address, so it will attempt to bind to all available network interfaces that includes private IP like 192.168.x.x, 10.x.x.x, etc; which in turns, may/will trigger the firewall prompt.

Signed-off-by: riasat <11375716+crimsonvspurple@users.noreply.github.com>
@crimsonvspurple crimsonvspurple changed the title Bind to loopback address only for Interactive Request Bind to Only Loopback Address When Making Interactive Request Mar 11, 2024
@crimsonvspurple crimsonvspurple changed the title Bind to Only Loopback Address When Making Interactive Request Bind to Only Loopback Address(es) When Making Interactive Request Mar 11, 2024
@Avery-Dunn Avery-Dunn self-assigned this Mar 11, 2024
Copy link
Collaborator

@Avery-Dunn Avery-Dunn left a comment

Choose a reason for hiding this comment

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

Sorry for the delay on this, but it looks good to me. This fix will be in our next release this week.

@Avery-Dunn Avery-Dunn merged commit 9c7636b into AzureAD:dev Mar 25, 2024
1 check passed
@Avery-Dunn Avery-Dunn mentioned this pull request Mar 25, 2024
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