Re: port forwarding and secured connection
- From: "Richard E. Silverman" <res@xxxxxxxx>
- Date: 18 Jan 2006 20:52:15 -0500
> Yes, I agree with you, but that does not answer to my question.
It answers the question you asked: "then why do I see TCP between B and
C". Perhaps it does not answer the question you meant to ask.
> I can connect with ssh, when listening to port, it is unreadable.
> That's correct.
I assume by "listening to port" you mean snooping the TCP traffic carrying
the SSH connection.
> The problem is I can see login and password between C and D when
> listening to port.
We already established that the C->D connection is not secured by SSH, so
this is expected.
> But when using forwarding, from a telnet for example, it is never
> unreadable.
I don't understand this sentence at all. First, an SSH port forwarding
situation is implicit in the previous statement, so I don't understand the
meaning of "But when using forwarding..." Second, "it is never
unreadable" means "it is always readable," just like the last connection
referred to (C->D), so I don't understand what juxtaposition you're trying
to set up.
--
Richard Silverman
res@xxxxxxxx
.
- Follow-Ups:
- Re: port forwarding and secured connection
- From: titeuf.tuti@xxxxxxxxxxxx
- Re: port forwarding and secured connection
- References:
- port forwarding and secured connection
- From: titeuf.tuti@xxxxxxxxxxxx
- Re: port forwarding and secured connection
- From: Richard E. Silverman
- Re: port forwarding and secured connection
- From: titeuf.tuti@xxxxxxxxxxxx
- Re: port forwarding and secured connection
- From: Richard E. Silverman
- Re: port forwarding and secured connection
- From: titeuf.tuti@xxxxxxxxxxxx
- port forwarding and secured connection
- Prev by Date: Re: SSH encryption
- Next by Date: Re: SSH encryption
- Previous by thread: Re: port forwarding and secured connection
- Next by thread: Re: port forwarding and secured connection
- Index(es):
Relevant Pages
|
|