Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Port forwarding confusion

Subject: Re: Port forwarding confusion
Date: Fri, 24 Aug 2007 21:59:43 +0200
Thanks for your input. Excuse my naiveness, but assuming I want to do the same 
for ldap/sieve and co: can I do that through the same 2022 tunnel or do I 
need a new one for each protocol?

Thanks, Joh

On Friday 24 August 2007 21:34:12 Joseph Spenner wrote:
--- Johannes Graumann

<johannes.graumann@googlemail.com> wrote:
I'm in a firewalled LAN which provides a ssh-proxy
to access outside machines
which I have to use like so:

1) build tunnel
ssh ProxyUser@SSHPROXY -L 2022:OUTSIDEBOX:22

2) make connection
ssh -X OutsideboxUser@localhost -p 2022

What I now wish to do is to access an outside
mailserver (especially port 993)
through this proxy.

Assuming OUTSIDEBOX can connect to your
OUTSIDEMAILSERVER, you should be able to connect using
the tunnel in #1, then another tunnel:

2a) ssh OutsideboxUser@localhost -L
9993:OUTSIDEMAILSERVER:993 -p 2022

Then point your email client at localhost:9993






___________________________________________________________________________
_________Ready for the edge of your seat? Check out tonight's top picks on
Yahoo! TV.
http://tv.yahoo.com/


Attachment: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>