Re: RemoteTelnet

[Alain Magloire]

> 
> >   Topic:
> >
> >    1. Re: Remote Telnet (Alain Magloire)
> >
> 
> Hello ,
> Thanks for the reply,
> 
> The current implementation of telnet client and daemon for pSOS  is
> available in the form of
> a library and source code is not available.
> inetd is used in unix based implementations but not in pSOS. Here in pSOS
> its a proprietary
> implementation which uses the pSH shell provided by pSOS. Remote telnet is
> not supported
> by this vesion. I have checked whether the other side is accessible on
> network (i.e ping is
> successful)
> The error message is proprietary pSOS msg which indicates "remote telnet is
> not supported".
> The pSOS machine supports a console login on serial port. I am able to
> telnet to other machines
> from the console login.If the other machine is unix based i am able to
> telnet further to other machines
> in that session. this means  telnet daemon on pSOS does not support another
> telnet in its shell.
> 
> Also the  tty, pty pair being used in unix implementation is not available
> in pSOS.
> Does  this  (tty/pty ) seems to be the problem ?

Sorry for the delay.
I do not know, pSOS is an RTOS that I've never deal with.
The tty/pty pair is the way "Unix" implementation does it.
After inetd spawns telnetd, telnetd will create pty pairs to initiate
the session transaction, this will permit programs like vi, emacs etc ..
who needs some sort of tty emulation to work.  There is a negotiation 
between the client and the server to establish the terminal settings.
Now, I'm not saying that is the problem.  I simply do not have enough
background with pSOS to say something remotely intelligent on what
the source of the problem.  A pSOS guru or there support lines would be
more appropriate.

> Regards,
> Vidyadhar.
> 
> 
> 
> > Message: 1
> > Subject: Re: Remote Telnet
> > To: address@hidden (Vidyadhar Watve)
> > Date: Thu, 23 Nov 2000 23:45:26 -0500 (EST)
> > From: "Alain Magloire" <address@hidden>
> > Cc: address@hidden
> >
> > >
> > > Hello ,
> >
> > Bonjour
> >
> > > I am working on pSOS OS (RTOS)  and the target is intel i960 processor.
> > > The pSOS network library supports telnet but "remote login" is not =
> > > supported.
> > >
> > > i.e I can telnet to a machine running pSOS with telnet option =
> > > enabled.But
> > > within that telnet session i am not able to telnet to another host.
> >
> > What's the message error, maybe the other host is not
> > running inetd with telnetd enable, did you try to telnet to
> > other host that you know provide telnet login services ?
> > Can you reach other hosts ? .i.e ping them or contact
> > them for example via finger rlogin daytime etc ...
> > Is it a DNS problem ? Is the other hosts running inetd
> > or somesort of telnetd serer standalone ?
> >
> > > telnetd in netutils for unix supports this functionality.
> >
> > Well, is not telnetd that lets you telnet to another session
> > when you are already in a telnet session.  When you contact
> > a host via telnet Protocol, assuming you have a running TCP/IP
> > stack and you can reach the other host via ping etc ...,
> > inetd(on the remote host) will answer an spawn a telnetd session for you.
> >
> > > I need to port the unix version telnetd to pSOS. What components / =
> > > states might
> > > be missing in pSOS which are present in netutils that could overcome =
> > > this problem.
> >
> > A running TCP/IP networking stack, The berkeley socket API and
> > terminal capabilities.
> >
> > I'm not sure if this a OS(pSOS) problem or you have
> > misconfigure your OS, in any case your best bet
> > is to consult your local pSOS networking guru.
> >
> > > The src code for pSOS telnet lib is not available.
> > >
> > > Regards,
> > > Vidyadhar.
> > >
> >
> > --
> > alain
> >
> >
> >
> > --__--__--
> >
> > Message: 2
> > Subject: syslogd security ?
> > To: address@hidden
> > Date: Thu, 23 Nov 2000 23:58:36 -0500 (EST)
> > From: "Alain Magloire" <address@hidden>
> >
> > Bonjour
> >
> > Good news, cast is off ... ye !!! A few physio workout and I'm
> > back rocking.
> >
> > Bad news, my machine's been crack.  I left my machine
> > running as a way to test the inetutils tools, ftp rlogin etc ...
> > except that I forgot to update inetd and syslogd.  So
> > both(ined and syslogd) were the default stock from Red Hat 6.1 (or
> > was it 5.2 ???)
> > Now I can not confirm is this was a syslogd buffer overflow
> > thing or another inetd services ...
> >
> > Speculation ?
> >
> > In any case excerpt from a syslogd messages:
> >
> > ---------------syslogd /var/log/messages ---------------------------
> > Nov 20 15:08:12 reliant
> > Nov 20 15:08:12 reliant syslogd: Cannot glue message parts together
> > Nov 20 15:08:12 reliant 173>Nov 20 15:08:12 rpc.statd[504]: gethostbyname
> error
> >
> > ******** Followed by a big blurb of non  printable characters ..
> >
> > Nov 20 15:09:11 reliant useradd[27892]: new group: name=proc, gid=3108
> > Nov 20 15:09:11 reliant useradd[27892]: new user: name=proc, uid=3108,
> gid=3108,
> >  home=/home/proc, shell=/bin/bash
> > Nov 20 15:09:16 reliant PAM_pwdb[27893]: password for (proc/3108) changed
> by ((n
> > ull)/0)
> > Nov 20 15:09:39 reliant PAM_pwdb[27895]: (login) session opened for user
> proc by
> >  alain(uid=0)
> > ---------------syslogd /var/log/messages ---------------------------
> > --
> > au revoir, alain
> > ----
> > Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!
> >
> >
> >
> > --__--__--
> >
> > Message: 3
> > Date: Fri, 24 Nov 2000 12:12:27 +0100
> > From: Marcus Brinkmann <address@hidden>
> > To: Alain Magloire <address@hidden>
> > Cc: address@hidden
> > Subject: Re: syslogd security ?
> > Organization: Marcus Brinkmann's Home
> >
> > On Thu, Nov 23, 2000 at 11:58:36PM -0500, Alain Magloire wrote:
> > > Good news, cast is off ... ye !!! A few physio workout and I'm
> > > back rocking.
> >
> > Great!
> >
> > > Bad news, my machine's been crack.
> >
> > Barf!
> >
> > > I left my machine
> > > running as a way to test the inetutils tools, ftp rlogin etc ...
> > > except that I forgot to update inetd and syslogd.  So
> > > both(ined and syslogd) were the default stock from Red Hat 6.1 (or
> > > was it 5.2 ???)
> > > Now I can not confirm is this was a syslogd buffer overflow
> > > thing or another inetd services ...
> > >
> > > Speculation ?
> > >
> > > In any case excerpt from a syslogd messages:
> > >
> > > ---------------syslogd /var/log/messages ---------------------------
> > > Nov 20 15:08:12 reliant
> > > Nov 20 15:08:12 reliant syslogd: Cannot glue message parts together
> > > Nov 20 15:08:12 reliant 173>Nov 20 15:08:12 rpc.statd[504]:
> gethostbyname error
> >
> > That's an old exploit of rpc.statd in the nfs package. Debian has an
> > announcement from Jul 2000 here:
> > http://www.debian.org/security/2000/20000719a
> >
> > This has nothing to do with syslogd in particular. It's just that the full
> > blurb of non-printable is too long to fit in the message buffer, and thus
> > truncated. Note that our version of syslogd doesn't support multiple
> message
> > parts, and will truncate even earlier.
> >
> > I wouldn't hold my hand in fire for my analysis, but I think it is
> correct.
> >
> > Thanks,
> > Marus
> >
> > --
> > `Rhubarb is no Egyptian god.' Debian http://www.debian.org
> address@hidden
> > Marcus Brinkmann              GNU    http://www.gnu.org    address@hidden
> > address@hidden
> > http://www.marcus-brinkmann.de
> >
> >
> >
> > --__--__--
> >
> > _______________________________________________
> > Bug-inetutils mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/bug-inetutils
> >
> >
> > End of Bug-inetutils Digest
> >
> 
> 
> 
> _______________________________________________
> Bug-inetutils mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-inetutils
> 


-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!