But it looks like the do not care and are doing nothing about it, by stating:
--remote-debugging-address switch presents a security issue and should not be used. We are planning to remove it from the old headless and there are no plans to implement it in the new headless.
I looked around the chromium source code, and figured out this patch to force 0.0.0.0 instead of 172.0.0.1:
Describe the bug Chromium removed the --remote-debugging-address=0.0.0.0 option, now it does nothing.
There is this issue open https://issues.chromium.org/issues/41487252, [bug] Flag
--remote-debugging-address
does not work as expectedBut it looks like the do not care and are doing nothing about it, by stating:
I looked around the chromium source code, and figured out this patch to force 0.0.0.0 instead of 172.0.0.1:
Can we manage to include our own patched chromium with this fix or can we use something like, this, which will forward port ip:9222 to localhost:9223:
Related:
225
158