Skip to content

Conversation

Crypt-iQ
Copy link

@Crypt-iQ Crypt-iQ commented Mar 2, 2021

Otherwise, debugging information is exposed if the port is reachable.

Otherwise, debugging information is exposed if the port is reachable.
@@ -77,7 +77,7 @@ func start() error {
}

go func() {
listenAddr := net.JoinHostPort("", config.Profile)
listenAddr := net.JoinHostPort("127.0.0.1", config.Profile)
Copy link
Contributor

Choose a reason for hiding this comment

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

there are very valid use case for allowing profiling on a externally reachable port though. Could we make the config.Profile option optionally set this IP?

@halseth halseth requested a review from guggero March 5, 2021 08:56
Copy link
Contributor

@guggero guggero left a comment

Choose a reason for hiding this comment

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

👍 for making this configurable. How about this: We change the config.Profile to a string and parse it. If it's just a number (e.g. to not break existing users that have the flag set), we use 127.0.0.1 as the host. If it's a host:port pair, use that directly.
Same for the other repos where this was proposed.

@lightninglabs-deploy
Copy link
Collaborator

@Crypt-iQ, remember to re-request review from reviewers when ready

@guggero guggero mentioned this pull request Sep 23, 2022
1 task
@guggero
Copy link
Contributor

guggero commented Sep 23, 2022

Replaced by #391.

@guggero guggero closed this Sep 23, 2022
positiveblue pushed a commit to positiveblue/pool that referenced this pull request Oct 11, 2022
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.

5 participants