|
I am not going to open port 22. The only ports that will be open are 80 and 443. So my ssh client will have to somehow "tunnel" over one of these two ports. I prefer 443 as that can be wrapped in SSL security too.
I'll post the solution here when I have one. I'm pretty certain this can be done. I have the bricks but need to get the mortar.
beejay you mention ldap. This is just a directory service - I already use it as my central user-data repository on my domain controller. I'm not sure how it fits into a web tunnelling scheme ?
|