Howto do Secured ssh from port https or port80(standard) to ssh d listening port 22 ?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Howto do Secured ssh from port https or port80(standard) to ssh d listening port 22 ?
Howto do Secured ssh from port https or port80(standard) to ssh d listening port 22 ?
====
I guess it is call tunneling, it is not easy to do i guess for novice.
The idea: there is a pc behind a nat that wanna ssh a distant pc listening port 22. We would like it secured. Is there a way ?
Is there any hints to do so, usually on the net , it is not meant for linux newbies and too dificult. Is slow step by step detailed information would be grateful.
I guess it is call tunneling, it is not easy to do i guess for novice. The idea: there is a pc behind a nat that wanna ssh a distant pc listening port 22. We would like it secured. Is there a way ?
Using OpenSSH *is* secure, else it wouldn't be called Secure SHell. If you would still want to tunnel ssh this command creates a tunnel from your local port 80 to a remote server running SSH whose IP address is 10.0.1.1: "ssh -L80:127.0.0.1:22 -t -N -2 10.0.1.1". Once authenticated in another window executing "ssh -p 80 localhost 'hostname -i' " should show the remote servers IP address. Note the local port 80 is just an example since ports below 1024 can only be forwarded by root, so if you're not root try for example 8080. If you work with tunnels a lot then it's no fun running and checking them: automate it using AutoSSH. For more interesting tunnel examples and explanation: http://souptonuts.sourceforge.net/sshtips.htm.
I guess it is call tunneling, it is not easy to do i guess for novice. The idea: there is a pc behind a nat that wanna ssh a distant pc listening port 22. We would like it secured. Is there a way ?
Using OpenSSH *is* secure, else it wouldn't be called Secure SHell. If you would still want to tunnel ssh this command creates a tunnel from your local port 80 to a remote server running SSH whose IP address is 10.0.1.1: "ssh -L80:127.0.0.1:22 -t -N -2 10.0.1.1". Once authenticated in another window executing "ssh -p 80 localhost 'hostname -i' " should show the remote servers IP address. Note the local port 80 is just an example since ports below 1024 can only be forwarded by root, so if you're not root try for example 8080. If you work with tunnels a lot then it's no fun running and checking them: automate it using AutoSSH. For more interesting tunnel examples and explanation: http://souptonuts.sourceforge.net/sshtips.htm.
ahh
I will try with putty behind the nat ...
will be not easy to set up the putty ; we like
(another day with ssh)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.