Kyle Hargraves wrote:

> >
> > > > Unless you chose the "server" install, by default Mandrake
> > > > doesn't install the telnet server.  Or any servers for that matter.
> > >
> > >     Actually this is not correct.  True - inetd must be assigned
> > >     a run level but from the above responses - OBVIOUSLY tcp
> > >     (telnet) services are installed.  Afterall - I can telnet OUT
> > >     but some weir'ed Mandrake'ism is preventing the connection
> > > inbound
> >
> > The telnet daemon is a separate install in mdk... just install the
> > rpm. Can't  think of the name...
>
>         .mmm weired !!   I suppose we're being saved from
>         ourselves are we ?

Not weird. Entirely sensible. Telnet is a legacy protocol that should ba banned both
inside and outside your network, and the client shoudl only be used for talking to
other misbehaving services for HTTP, SNMP, etc. diagnosis. Distributions shouldn't
install Telnet servers, and if Mandrake wanted to be even better, they should not
include a Telnet server with their distro.

Mike

>
>
> > Well, no. Telnetting out is a completely different issue then
> > telnetting  in. You use telnet as client and telnetd to accept
> > connections.
>
>         yes agreed - and inetd.conf has the approprite
>         entries; see following paragraph
>
> > Did  you  check whether the receiving service is in fact running:
>
>         yes - as I mentioned in a previous post I had to set the
>         run level for inetd - so it would staff in rc3.d
>
> > service inetd status
> > or
> > service xinetd status
>
>         Now the follwing is weired !
>
> [root@purcell xinetd.d]# service inetd status
> inetd: unrecognized service
>
>         BUT
>
> [root@purcell xinetd.d]# ps aux |grep inet
> root       369  0.0  0.3  1100  520 ?        S    Jan21   0:00 inetd
> root      5888  0.0  0.7  1940  944 ?        S    10:58   0:00 xinetd -reuse -pi
>
> Now, there are appropriate entries in /etc/inetd.conf for telnet but
> they don't seem to observed.  There is nothing in xinetd.d for telnet
> which is probably the problem.  That is, it seems that xinetd seems
> to have taken over.  (BTW I started it from  inet.d)
>
> could someone send me an /etc/xinetd.d/telnet.conf  please ?
>
> Also, someone asked about the security level
>
> [root@purcell xinetd.d]# echo $SECURE_LEVEL
> 4
>
> cheers,
>
> Kyle Hargraves (and thanks for the assistance to date)

--
------------------------------------------
Mike MacCana     Support Consultant
          C Y B E R S O U R C E
   Level 9, 140 Queen St Melbourne 3000
Ph : +61 3 9642 5997 Fax: +61 3 9642 5998



Reply via email to