![]()
In order to have a proper display of characters in your putty, you need to set the encoding of putty accordingly to your linux box configuration (mostly UTF-8 or your country's specific charset). Adding more zeros could lead putty the behave strangely. Replace the 200 value by 20000000 (it should be enough). This is not really a mandatory step, but really usefull. In Saved sessions, enter a string that remind you your trully loved linux box o) In the port field, enter 443 (or 80 if you use the 80 port) In the hostname field, enter the ip or domain name of your linux box. of course) by right clicking in the title window->change settings. Putty is a marvelous ssh client for windows, I couldn't live without it.Īll settings describe below can be change on the fly when the ssh connection is open (except for the proxy setting. ![]() Once this is done, you can test it by trying to open an ssh connection on the port 443, or use telnet (telnet youBoxIp 443) and you should see you open ssh server version : SSH-2.0-OpenSSH_3.9p1. ![]() Where 80.1.1.1 is my external public ip address. If this can help, here is the lines of my iptables-save output that involves the 443 port : #Ssh tunnel manager http proxy from command line how to#You can find information on how to do that here : With the sme server, i've such a tools (a web interface attainable only though my local network) You may even have a graphical interface that allow you to do that easily. You can redirect you 443 port to the 22 port using iptables or other tools. I prefer the second option that leaves untouch the ssh server configuration, and let your linux box be accessed trough ssh on it's standart port. We can either change the ssh server setting to listen on port 443 or redirect the connection established on the 443 port to 22 port. What we need is that your linux box accepts a ssh connection on the tcp/443 port. But you can do the same with tcp/80 port. The proxy allow tcp/80 & tcp/443.Īs the tcp/80 is probably used by your web server, we'll focus on tcp/443, the https port which you probably don't need. The ssh server usually listen on the tcp/22 port, but this port is filtered by the proxy. You're a geek like me, so you have a linux box somewhere running 24hours a day running a ssh server in a linux box. ![]() The following post will show you a way to bypass a proxy with NTLM authentication mecanism. This blog post will show you how to bypass an http proxy with a basic authentication. Doing that allow you to bypass the content filtering and security. So here is what to do, to get an SSH connexion to a linux box.īut beware that doing that will certainly break the security contract you signed when you enter the company. So no tcp/22 for SSH, and I miss it really much for many reasons. Those proxy allows http (tcp/80) and https (tcp/443) connections and nothing else. ![]() Useful for the company securtity and efficiency, but really borring for me. #Ssh tunnel manager http proxy from command line software#I'm working for an IT Services & Software Engineering company, and I often work for some time (3 months to a year) by the client company's office.Īnd often, I'm behind a ****ing proxy that filters http request, provide antivirus analysis etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |