Hey All,
A firewall cannot tell the difference btwn a telnet connection and a smtp
connection, that I am aware of. Telnet doesn't really do anything special
beside open a connection to a particluar port (usu. 23). In addition to
that many smtp's have to be configured to allow for somewhat non-sta
On Fri, 07 Jul 2000 16:34:30 -0400, "Susannah D. Rosenberg" <[EMAIL PROTECTED]>
said:
>packet filtering mean anything to you?
I understand the concept. I'm stating that there's no way you can
tell a TCP SYN on port 25 from an MTA from a TCP SYN on port 25 from
telnet. They look exactly the s
[EMAIL PROTECTED] wrote:
>
> On Fri, 7 Jul 2000 15:14:59 -0400 , "Fan, Laurel" <[EMAIL PROTECTED]> said:
>
> >If I can, from my computer, open an "smtp connection" to port 25 on
> >somehost, I can run "telnet somehost 25". Neither of which has
> >anything at all to do with telnetd.
>
> I am in
On Fri, 7 Jul 2000 15:14:59 -0400 , "Fan, Laurel" <[EMAIL PROTECTED]> said:
>If I can, from my computer, open an "smtp connection" to port 25 on
>somehost, I can run "telnet somehost 25". Neither of which has
>anything at all to do with telnetd.
I am indeed at a loss to tell how a firewall coul
Susannah D. Rosenberg, [EMAIL PROTECTED], said:
> yep. but there's a difference between being able to /telnet/ to port 25,
> and opening an smtp connection to port 25.
No, there is not.
Unless by "telnet" you mean something besides "run a program named telnet
and connect to port 25". (In which
"Fan, Laurel" wrote:
>
> Susannah D. Rosenberg, [EMAIL PROTECTED], said:
> > yeah, but it still leaves rlogind and telnetd flapping in the wind. can
> > you say "telnet to port 25", boys and girls?
> >
> > gaping security flaws are /bad/.
>
> Taking out rlogind and telnetd won't close port 25.
