the fast, reliable localhost tunneling solution


Disable the HTTP proxy from SSH

2013-08-19, 08:46

Hello,

I just have a short question. I asked in the chat several times, but I think I always missed the mods, and now I'm asking here.

So, is it possible that I can disable the HTTP proxy?

Like, that the SSH is just "[myservername].pagekite.me:22" instead of the 443 Proxy?

Because that'd be much easier than with proxy. E.G. on Ubuntu. There I had to download corkscrew, because of the Proxy. On Windows with PuTTY it's no problem..

Or what would be if I say the ssh daemon, it should listen on port 443? Can I connect by just typing "sudo ssh user@[myservername].pagekite.me 443"? Would that work?

Or is there any other way to solve this?

Oh, and by the way, when I try to go via SSH to my PC with my mobile phone with an SSH app. I have to chance to use a Proxy. But the proxy always wants me to write down a password. But as much as I know the pagekite proxy which is used for SSH doesn't require any login informations. That's another reason to disable the proxy :)

Thanks for your help!

Aw and sorry for my.. maybe a little bit strange.. english, but it's not my native language, so please excuse me :D

Have a nice day!!

Comments

  1. Bjarni RĂșnar Einarsson said on 2018-01-02, 17:46
    No, the PageKite SSH solution requires configuration of an HTTP proxy.

    It can not be disabled.

    Some other solutions work without a proxy because they give you a raw TCP port. However, the port will change every time you run their tools. The port is also public and easily probed by hostile parties - there are only about 65000 possible ports on each relay server, which makes it relatively easy for an attacker to try all the numbers and find your SSH server.

    With PageKite you configure things to use a specific name and the HTTP proxy, and then it will work the same every time after that - you don't need to change it every time. You can even configure your SSH client to automatically do the right thing for all names
    ending in *.pagekite.me, if you have many devices to connect to. So although it may be a little more work to get started, it will be less work in the long run.

    This is also more secure, since there are an infinite number of different pagekite names possible, so the enumeration attack you can use against the port-based TCP proxies do not work against PageKite.
    Permalink

Leave a comment

( (Please leave these blank: )

We use Gravatar for commenter's photos. Get your own, it's free!