4 ms·

1. I got this $ ssh -R 2000:localhost:8080 localhost.run The authenticity of host 'localhost.run (35.171.254.69)' can't be established. RSA key fingerpri

1. I got this $ ssh -R 2000:localhost:8080 localhost.run The authenticity of host 'localhost.run (35.171.254.69)' can't be established. RSA key fingerprint is SHA256:FV8IMJ4IYjYUTnd6on7PqbRjaZf4c1EhhEBgeUdE94I. Are you sure you want to continue connecting (yes/no/[fingerprint])? Make it so it prints the url without more input, so it can be called from scripts easily. Like this ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -R 80:localhost:8080 localhost.run 2. Then I got this Port 2000 is not allowed. Only port 80 and 443 are allowed. I didn't see easily that it's the 8080 I should change. 3. Can you make it so someone can control my xterm? This could be a useful (and dangerous, but also useful) feature. Check out https://github.com/paradoxxxzero/butterfly https://github.com/paradoxxxzero/butterfly

tommyvan 6y ago
Thanks for trying it and for such a detailed response! That host check prompt is a SSH security feature, it will only ask you the first time to accept the key and after that it will only check that the key hasn't changed, to verify no one is impersonating my ssh server, and allow you in without a prompt if it is ok. It's kind of like how your browser expects a valid certificate signed by a certificate authority when visiting https sites, but without the certificate authority. In most cases accepting the first time means you will never be asked again. Certainly the check can be skipped as you described tho if preferred tho. for port 2000 try this: ssh -R 80:localhost:2000 localhost.run The first port number needs to either be 80 or 443, and for most people 80 is the port they will use. the second port number is the port your local app runs on. https://localhost.run/docs/http-tunnels https://localhost.run/docs/http-tunnels explains what 80 does and https://localhost.run/docs/tls-passthru-tunnels https://localhost.run/docs/tls-passthru-tunnels 443, but 443 is for very specific use cases. Butterfly looks awesome! If i'm understanding what you're after you want to be able to run butterfly locally and give someone else an internet URL to connect to your butterfly server, right? I'm not clear on how authentication in butterfly works, I'd need to read more, but certainly you could do client x509 authentication with a TLS passthru tunnel (that's the 443 advanced use case I mentioned), altho I'm not sure if someone like letsencrypt does client certs, so you might need to live with a certificate warning in your browser unless you can get a CA signed client/server cert. Maybe butterfly allows other authn/authz methods tho, like username/password over http, in which case you could use a normal http tunnel and connect it to the internet. If I get a chance to try it I'll reply back, and you get it working before me pls let me know!
- repartix 6y ago
  xterm.js might help too. Now I want something more. I want to be able to run localhost.run locally and give someone else an internet URL to connect to my local xterm, or to my local X display (vnc?). I want them to see my text editor and type stuff in it.

tommyvan 6y ago

Thanks for trying it and for such a detailed response! That host check prompt is a SSH security feature, it will only ask you the first time to accept the key and after that it will only check that the key hasn't changed, to verify no one is impersonating my ssh server, and allow you in without a prompt if it is ok. It's kind of like how your browser expects a valid certificate signed by a certificate authority when visiting https sites, but without the certificate authority. In most cases accepting the first time means you will never be asked again. Certainly the check can be skipped as you described tho if preferred tho. for port 2000 try this: ssh -R 80:localhost:2000 localhost.run The first port number needs to either be 80 or 443, and for most people 80 is the port they will use. the second port number is the port your local app runs on. https://localhost.run/docs/http-tunnels https://localhost.run/docs/http-tunnels explains what 80 does and https://localhost.run/docs/tls-passthru-tunnels https://localhost.run/docs/tls-passthru-tunnels 443, but 443 is for very specific use cases. Butterfly looks awesome! If i'm understanding what you're after you want to be able to run butterfly locally and give someone else an internet URL to connect to your butterfly server, right? I'm not clear on how authentication in butterfly works, I'd need to read more, but certainly you could do client x509 authentication with a TLS passthru tunnel (that's the 443 advanced use case I mentioned), altho I'm not sure if someone like letsencrypt does client certs, so you might need to live with a certificate warning in your browser unless you can get a CA signed client/server cert. Maybe butterfly allows other authn/authz methods tho, like username/password over http, in which case you could use a normal http tunnel and connect it to the internet. If I get a chance to try it I'll reply back, and you get it working before me pls let me know!

repartix 6y ago
xterm.js might help too. Now I want something more. I want to be able to run localhost.run locally and give someone else an internet URL to connect to my local xterm, or to my local X display (vnc?). I want them to see my text editor and type stuff in it.