binding remote debugger interface out of local loopback

[Albert Yu]

It looks like the IP binding is hardcoded in the shell, that it will always use 127.0.0.1 for serving the remote debugging interface. That is nice, considering that the interface do not have any authentication control and it would be best to leave it contained. 

However, I have also tried to use docker to build a container for that. It turns out that, by listening 127.0.0.1, docker would not accept localhost traffic to talk to the container. The alternative is to use `-host=net`, which expose the whole network stack in the container to the localhost, but I find that less desirable. 

Currently, I use a code patch to replace 127.0.0.1 in the source code with 0.0.0.0 to build the container. I have it uploaded to docker registry in hub.docker.com/r/yukinying/chrome-headless/, please feel free to take a look if that would help.

And is it possible to provide an optional switch, such that the address binding would be relaxed? It will be extremely useful for people to build container with it.

Thank you!

[Sami Kyostila]

That seems like a good reason to add a command line switch for this: https://codereview.chromium.org/1920773003/ 

- Sami

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/ff3c105d-1146-4670-bb06-b277c5144852%40chromium.org.

[jean...@gmail.com]

Do you know if this option is in chrome right now ? 

Tried to add --remote-debugging-address=0.0.0.0 but it does not work.

[Sami Kyostila]

Yes, that flag should work (only together with --headless and --remote-debugging-port however).

- Sami

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/c5574c6b-05ca-47ad-824d-3e2dd870612a%40chromium.org.

[Jean DAT]

Using --remote-debugging-address=0.0.0.0 did not worked for me but it worked with an IP like 192.168…

You received this message because you are subscribed to a topic in the Google Groups "headless-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/headless-dev/WV5-fVfLW0I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to headless-dev...@chromium.org.

To post to this group, send email to headle...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/CAPuLczujDeuaZU_ko24NWeQzSpp7a1LW5icwPE0DZVOJAOVxLQ%40mail.gmail.com.