On Mon, 2005-04-18 at 13:14 +0200, Christian TrÃster wrote: > Hi, Hi Christian, thanks for your response.
[...] > > 1) From inside firewalls that allow only web (http) access via a proxy > > (work) > I have had luck using another port for ssh. Sometimes firewalls permit news > access via port 119 - and also ssh on 119 ;) Locked down where I am currently unfortunately. Though I guess I could use port 80, since all my access is now via the SSL port. I'll bear that in mind. > > 2) From a machine with internet access, but no ssh client, and no > > possibility of installing one (cafe, friends) > For Windows there is a putty.exe available on the putty website which does > not > need to be installed. Works pretty fine. Ah, forgot about that. Guess that helps with the internet cafe situation. Though once I get the following sorted, I should be able to use any browser with internet access. > > > My initial research led me to the following: > > http://freshmeat.net/projects/sshwebproxy/ I decided to go with this in the end, wanted something to get my teeth into. Certainly got that. :) Got it working after a struggle, there is minimal documentation, and I had to install tomcat. So, as I said, working from inside the LAN OK, just need to get apache2 and tomcat4 talking to each other now, so that it is available from a browser. > > http://freshmeat.net/projects/cgi-shell/ I didn't look at this seriously once I decided to go with sshwebproxy. > I have never tried one of these... > > Bye, Christian Bye and thanks. -- "Don't tell me I'm burning the candle at both ends -- tell me where to get more wax!!" -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
