search for: ip_of_web_site_to_access_from_remot

Displaying 4 results from an estimated 4 matches for "ip_of_web_site_to_access_from_remot".

2020 Nov 12
3
run firefox via an ssh tunnel
If the point is to access a specific web site only the remote machine can get to, you can also do it with port forwarding: ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine and then locally run any browser, and access https://localhost:443 (assuming it's https. If it's plain http, use "http" and 80). Note that you'll be breaking some aspects of https security such as man-in-the-middle protection and perhaps others, and you...
2020 Nov 12
0
run firefox via an ssh tunnel
On Thu, Nov 12, 2020 at 12:56:15PM +0000, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote: > > If the point is to access a specific web site only the remote > machine can get to, you can also do it with port forwarding: > ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine > and then locally run any browser, and access > https://localhost:443 > (assuming it's https. If it's plain http, use "http" and 80). Note > that you'll be breaking some aspects of https security such as > man-in-the-middle protection and...
2020 Nov 11
2
run firefox via an ssh tunnel
On Wed, 11 Nov 2020 at 17:45, R C <cjvijf at gmail.com> wrote: > I do it all the time. > > > make sure you forward X11, on the ssh server side, and login with > ssh -X me at myhost.whatever > > start firefox with: > > /usr/bin/firefox -no-remote if you don't want the remote pages ending > up in your local browser > > or if you don't care,
2020 Nov 12
3
run firefox via an ssh tunnel
...n Billings wrote: > On Thu, Nov 12, 2020 at 12:56:15PM +0000, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote: >> If the point is to access a specific web site only the remote >> machine can get to, you can also do it with port forwarding: >> ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine >> and then locally run any browser, and access >> https://localhost:443 >> (assuming it's https. If it's plain http, use "http" and 80). Note >> that you'll be breaking some aspects of https security such as >> man-in-the-mi...