nassh: secure shell port forwarding drops connections. |
||||||||
Issue descriptionChrome Version: 68.0.3416.0 (Official Build) dev (64-bit) OS: ChromeOS What steps will reproduce the problem? (1) Unzip the attached http-test.zip on linux machine. (2) Run python -m SimpleHTTPServer from that directory (serving it on port 8000) (3) Open secure shell on chromebook (4) Connect to that linux machine's SSH server forwarding the test http port (i.e. SSH Arguments: -L 8000:localhost:8000) (5) Open http://localhost:8000 on the chromebook What is the expected result? Expect all of the html and css files to load, making each paragraph green. What happens instead? Often, one or more resources fail to load. This results in some of the paragraphs being red or the html itself being blank - i.e. blank page. Refreshing with shift+reload you can see different sets of requests succeed.
,
May 30 2018
@flackr, why is step #4 required? We are talking to Chrome dev tools folks about making linuxhost a secure origin, so it should be treated the same as localhost.
,
May 30 2018
This bug is about the secure shell app (https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo?utm_source=chrome-app-launcher-info-dialog) dropping connections when you use its port forwarding feature. I realize that there are other ways to solve the local linuxhost use case but secure shell port forwarding is also useful for testing web servers on a remote host (without exposing the webserver publicly and getting secure origin treatment).
,
May 30 2018
this is a legit bug regardless of what we decide to do on the crostini side
,
May 31 2018
As an update, I wrote a tool to do a better test, see attached index.html. I ran three tests of 1000 connections. The success rate was the following: 54.9% success rate using ssh relay (--config=) forward to my desktop 97.8% success rate using direct ssh forward to linuxhost 97.3% success rate using direct ssh forward to an external computer 100% success rate on a control test (direct http connection to external computer)
,
Nov 7
I see this issue connecting to my dev server through tunnels. I see it on multiple chromebooks and networks. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 Deleted