Path: utzoo!news-server.csri.toronto.edu!rutgers!ucsd!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!jpradley!jpr
From: jpr@jpradley.jpr.com (Jean-Pierre Radley)
Newsgroups: comp.dcom.modems
Subject: Re: SCO Unix uucico RTS/CTS (was re:T2500 -> TB+ spoofing problem)
Keywords: uucp spoofing T2500 TELBIT
Message-ID: <1991Mar13.001850.20702@jpradley.jpr.com>
Date: 13 Mar 91 00:18:50 GMT
References: <1991Mar7.214200.20682@hq.demos.su> <1991Mar10.014152.26911@jpradley.jpr.com> <27682@netcom.COM>
Organization: NYC Public Unix
Lines: 23

In article <27682@netcom.COM> gandrews@netcom.COM (Greg Andrews) writes:
>In article <1991Mar10.014152.26911@jpradley.jpr.com> jpr@jpradley.jpr.com (Jean-Pierre Radley) writes:
>>
>>   [quoting his earlier post]
>>
>>>>Whatever I do in my dialTBIT binary, or any chat script, SCO's uucico will
>>>>ALWAYS set:  -ctsflow -rtsflow -ixon -xoff -ixany.
>
>That's on dial-out.  What does it do for dial-in if you have CTSFLOW
>enabled in your /etc/gettydefs?

Same thing.

>Are you certain it's uucico doing that?  Could it be uuchat as the
>Systems file chat script is processed?  (just a thought, and I don't
>know how to run dialTBIT and uucico on the port without uuchat in
>between...)

I'm just stating that what I observe is: no matter what a compiled dialer does,
or what uuchat does reading a chat script, uucico resets things when those have
terminated.

 Jean-Pierre Radley   NYC Public Unix   jpr@jpradley.jpr.com   CIS: 72160,1341