David, > From: "David B. Cook" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Date: Thu, 11 Oct 2001 09:47:28 -0400 (EDT) > > Port forwarding through ssh is a *fabulous* solution.
I am new to this (forwarding through ssh), but *indeed* it does look neat. > Look at Tunnelier (http://www.bitvise.com/tunnelier.html) for WinX > environments. Thanks! I am also investigating various other possibilities, PuTTY comes into the picture for me because it supports Public Key authentification whilst I don't think Tunnelier does (or am I wrong?). But on the other hand PuTTY doesn't appear to support configuration files and command line parameters (drat!). > I forward 137/138/139 to my house and I can use my Samba shares from > anywhere through an encrypted tunnel. OK, here comes the question: Yesterday I was playing with this, forwarding 137/138/139 through an encryted tunnel (still *on* the company network - I haven't yet punctured my LEAF Firewall!) from a Win NT box to a Linux box. Experiments with tunneling HTTP were easy, point browser at localhost or configure the browser with localhost as proxy and Bingo! However, how do I get the MS client software (this is for rodent bound road-warriors) to look into the tunnel? Or did you do it with SAMBA related tools on Linux? > MS functionality without their security problems! (I know, technically I > have extended the risk element on associated server procs from my server > to the end-of-line Windows device ... but don't burst my bubble!) Yeah, it's nice, but the worries persist... Greetings Mark _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
