Today, Benjamin Scott gleaned this insight:
> To do so, configure your SSH client to forward local TCP port 110 (which is
> POP3) to remote server TCP port 110. Do the same for TCP port 25 (SMTP).
> Then point your mail client to "localhost" for its mail servers. SSH will
> forward the connections over the secure tunnel to your mail servers, and your
> mail client will be none the wiser.
Every time I see this it fails to make sense to me... I can't see where
the encryption happens and where the protection is. Maybe you can explain
it, or maybe I'll have to go read the How-tos.
Basically my question is this: How does the POP server communicate with
the encrypted tunnel? Presumably it doesn't support encryption, which is
the whole point. So when it receives encrypted data from ssh on its end
of the socket, how does it get decrypted?
The only way this makes sense to me is if BOTH ends of the pipe are
redirected through ssh... I can't see how it will work any other way.
And it seems to me that that scenario only works if EVERYONE uses an
ssh-forwarded session to retrieve mail.
What am I missing?
-Baffled in North Andover :)
--
You know that everytime I try to go where I really want to be,
It's already where I am, cuz I'm already there...
---------------------------------------------------------------
Derek D. Martin | Unix/Linux Geek
[EMAIL PROTECTED] | [EMAIL PROTECTED]
---------------------------------------------------------------
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
