SSH Tunnels and Chrome / Chromium > v71

(Related to #18 (closed), #19 (closed))

The issue is related to subtleties in how name resolution works with a proxy. (In short, you can either send DNS requests through the tunnel, or you can send them to the internet from wherever you are. We want all traffic to go through the tunnel.)

Now, Chrome has good defaults for the common use case of proxies, but does not seem to handle the case where the proxy is listening on 127.0.0.1 / localhost standing for the loopback network interface of the machine I'm sitting in frot of, and the necessity that I also want to connect to 127.0.0.1 / localhost but this time meaning the loopback network interface of the remote machine my Jupyter is running on.

The obvious way out: Don't use 127.0.0.1 / localhost on the remote machine.

But this requires closer scrutiny, because

• there may be many IP addresses to use,
• there may be public IP addresses that are safe to use because the sysadmins of the remote machine made sure they are not visible from an untrusted network,
• there may be public IP addresses that should not be used, because you'd end up with your JupyterLab in the internet.

Let's think about how to proceed here.

Tagging people who suffer from this / might be interested or able to help: @jaard-hauschildt, @friederike-prowe, @arthur-prigent, @sebastian-wahl