If you use an untrusted machine D to bounce your traffic then you would need to do
some tunnelling to prevent someone on D from sniffing your traffic. If you simply type
"# ssh D ssh C" then your traffic is in the clear inside machine D. It is better to do
a tunnel like so:
# ssh -L2222:C:22 -f D sleep 5
# ssh -p 2222 localhost
If you don't have your own machine D outside the firewall then you could install a
Java applet on some web hotel. Check out www.mindbright.com for a great SSH client in
Java.
Amanda.
On Wed, 12 Jul 2000, [EMAIL PROTECTED] wrote:
> On Wed, 12 Jul 2000, Theo Van Dinter wrote:
> > If you have no admin access on C, you're kind of hosed unless you can get
> > an opening in the firewall. You would have to get access to a machine
> > D outside the firewall where you could SSH to using one of the above
> > methods, and then SSH from D to C.
>
> I think I am hosed, and will have to come up for a legitimate case
> for having our sys. admin. "open" up or "listen" on port 22 of the
> firewall. If I could only find a site related to chip design that requires
> me to login via ssh, I could go to my manager and make a business case,
> otherwise I'm hosed.
