From: Sys Admin (email_suppressed_at_lugwash.org)
Date: Sat 08-Feb-2003 08:45:36 PM EST
Instead of using putty for the tunnel part, ssh.com's ssh client has a
"tunnel only" option under Edit --> Settings --> Profile Settings -->
Connection --> Request tunnels only (disable terminal).
Putty probably has the same option somewhere, but i haven't used it
that much.
On 2003.02.08 15:05 Godwin wrote:
> Oh yeah, this does the trick. I can now use putty to start the ssh
> session
> to F1, then launch (gulp) ProComm to telnet over to S1 directly.
> Beautiful.
> Many thanks to all. Now, I just have to come up with a way of not
> giving
> shell access to the inital login account to F1. Perhaps have it run
> some
> kind of infinite loop or something. Hmm, it has to be something they
> can't
> break out of. Anyhoot, thanks again.
>
> regards,
> Godwin
>
>
>
> ----- Original Message -----
> From: "Dan Pritts" <[e-mail suppressed]>
> To: "Godwin" <[e-mail suppressed]>
> Cc: "lugwash" <[e-mail suppressed]>
> Sent: Friday, February 07, 2003 1:15 PM
> Subject: Re: [WLUG] Regular telnet through SSH Tunnel
>
>
> > If you create an SSH tunnel from PC1 to F1, with local port 23, and
> remote
> > host S1 and remote port 23, then telnetting to localohst on PC1 will
> > forward your session over the internnet over the SSH tunnel to the
> firewall,
> > which will then send the traffic in the clear over your internal
> > network to S1.
> >
> > The openssh syntax for this would be:
> >
> > ssh F1 -L 23:S1:23
> >
> >
> >
> > On Thu, 6 Feb 2003, Godwin wrote:
> >
> > > While borrowing the topic of ssh tunnels from the "TightVNC"
> thread,
> here's what I'd like to accomplish:
> > >
> > > PC1 is a Windows box sitting at home, F1 is a Linux
> firewall/gateway at
> work and S1 is an OpenVMS server at work.
> > >
> > > On F1, the only allowed traffic in from the world is via SSH on an
> obscure port. Also on F1, I have a user account with
> "/path/to/script" in
> the /etc/passwd file which will bounce the login to a telnet session
> on S1
> instead of a command prompt on F1 then close the SSH session once the
> user
> ends the telnet session on S1.
> > >
> > > The goal here is to have a user on PC1 use ProComm (gulp) to get
> to S1
> in a secure fashion. As you may know, ProComm doesn't support SSH -
> just
> telnet. What product could I use (hopefully open source) to start the
> ssh
> tunnel from PC1 to F1 and then use ProComm to telnet from PC1 to S1?
> > >
> > > Before you say: Why on earth would I want to do this, particularly
> with
> ProComm when I could use Putty or SecureCRT and just ssh in? Well,
> for some
> reason, the key mappings required for OpenVMS only seem to work well
> on
> ProComm, AND that's the only app. with which "management" is familiar
> and
> can support (for our clients).
> > >
> > > So, if anyone has any pointers, please chime in.
> > >
> > > thanks,
> > > Godwin
> >
> > dan pritts
> > [e-mail suppressed]
> > 734 996 0169
> >
>
>
> --
> *** Sent from [e-mail suppressed] *** http://www.lugwash.org
> to unsubscribe: `echo "unsubscribe" | mail
> [e-mail suppressed]`
>
-- *** Sent from [e-mail suppressed] *** http://www.lugwash.org to unsubscribe: `echo "unsubscribe" | mail [e-mail suppressed]`
This archive was generated by hypermail 2.1.5 : Sat 01-Mar-2003 01:00:03 AM EST