On 04/13/2011 08:17 PM, Simon Walker wrote: > On 13 April 2011 17:14, Jeremy Baron <jer...@tuxmachine.com > <mailto:jer...@tuxmachine.com>> wrote: > > Maybe someone should set up a TS login server sshd to listen on port > 443 aka https. (if it's not already claimed by a web service) > > An alternate SSH port would be trivial to set up, but 443 maybe isn't > the best port, as this would prevent possible future access to the > toolserver over https (unless it was changed)
If it's only on a login server, I don't see any problem. Those servers shouldn't be serving web pages anyway. Not sure if there's really that much need for it, though. > > On Apr 13, 2011 12:06 PM, "DeltaQuad" <deltaq...@live.ca > <mailto:deltaq...@live.ca>> wrote: > > > Can’t say right now as my school blocks FTP/SSH to the toolserver, > will let you know later today. > > Heh, I can't say I blame them. SSH was always my way around the > filtering at school, combined with portable firefox. (socks5 proxy using > dynamic port forwarding if you want to know :P) BTW, if you have access to an HTTP(S) proxy, you may be able to tunnel SSH over that. Just Google for "ssh over https". -- Ilmari Karonen _______________________________________________ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
