[comp.unix.i386] /etc/issue choking uucp logins

asv@gaboon.UUCP (Stan Voket) (12/25/89)

     I have a full screen /etc/issue that I'd like to display on unused
     terminals to clear a previous user's work for security and neatness.
     However, a full screen of anything is not what another machine likes or
     needs when trying to login for a uucp transfer.  It has caused remote
     logins to fail.  How can I display my large /etc/issue for local
     terminals but not on dialup lines?

     Thanks in advance!  :-)


-- 
+----------------------------------------------------------------------+
| - Stan Voket, asv@gaboon - OR - ...uunet!hsi!stpstn!gaboon!asv       |
|               Land Line: (203) 746-4489  TELEX 4996516             - |
+----------------------------------------------------------------------+

rock@rancho.uucp (Rock Kent) (12/26/89)

>>>>> On 25 Dec 89 05:13:56 GMT, asv@gaboon.UUCP (Stan Voket) said:
Stan>      I have a full screen /etc/issue that I'd like to display on
Stan>      unused terminals to clear a previous user's work for
Stan>      security and neatness.  However, a full screen of anything
Stan>      is not what another machine likes or needs when trying to
Stan>      login for a uucp transfer.  It has caused remote logins to
Stan>      fail.  How can I display my large /etc/issue for local
Stan>      terminals but not on dialup lines?

I can think of two possible approaches:

SIMPLE:  Assuming that all of your local terminals are known and have
similar screen control sequences, embed the *clear screen and home
cursor* control sequence into either the login prompt or the
/etc/issue and blow off the screen full of ascii graphics or whatever.

HARDER:  Get yourself a copy of a getty source (e.g. T William Wells'
getty.c copywrite 1989) and hack into it the intelligence to tell the
difference between different local and remote terminal lines.

NOTE that, although I am running Wells' getty under Microport V/386, I
haven't tried either of the above stunts and wouldn't bet my system on
the feasability of either one.  Let us know how it turns out.

***************************************************************************
*Rock Kent    rock@rancho.uucp        POB 8964, Rancho Sante Fe, CA. 92067*
***************************************************************************

cpcahil@virtech.uucp (Conor P. Cahill) (12/27/89)

In article <4927@gaboon.UUCP>, asv@gaboon.UUCP (Stan Voket) writes:
>      I have a full screen /etc/issue that I'd like to display on unused
>      terminals to clear a previous user's work for security and neatness.
>      However, a full screen of anything is not what another machine likes or
>      needs when trying to login for a uucp transfer.  It has caused remote
>      logins to fail.  How can I display my large /etc/issue for local
>      terminals but not on dialup lines?

Why not just use 40 or so return's which will clear most screens and will
not be so big as to fill up buffers of other systems trying to login.
-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+

bill@twwells.com (T. William Wells) (12/27/89)

In article <1989Dec26.062006.13829@rancho.uucp> rock@rancho.uucp (Rock Kent) writes:
: HARDER:  Get yourself a copy of a getty source (e.g. T William Wells'
: getty.c copywrite 1989) and hack into it the intelligence to tell the
: difference between different local and remote terminal lines.
:
: NOTE that, although I am running Wells' getty under Microport V/386, I
: haven't tried either of the above stunts and wouldn't bet my system on
: the feasability of either one.  Let us know how it turns out.

It would be trivial to add an option to mine to specify the file
to output instead of /etc/issue. In fact, I'll add it right now;
it was something I was thinking of doing anyway....It's done.

I have a new release of it which I will be submitting to
comp.sources.unix at the beginning of the year. If anyone
desperately needs it before then, I'll send it. But remember: if
I'm answering mail, I'm not writing code.

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.com

tim@comcon.UUCP (Tim Brown) (12/28/89)

In article <4927@gaboon.UUCP>, asv@gaboon.UUCP (Stan Voket) writes:
> 
>      I have a full screen /etc/issue that I'd like to display on unused
>      terminals to clear a previous user's work for security and neatness.
>      However, a full screen of anything is not what another machine likes or
>      needs when trying to login for a uucp transfer.  It has caused remote
>      logins to fail.  How can I display my large /etc/issue for local
>      terminals but not on dialup lines?
> 

Use uugetty.  It doesn't use the issue file at all.  Works for me.

Tim Brown                           |
Computer Connection                 |
(attmail or uunet)!comcon!tim       |

asv@gaboon.UUCP (Stan Voket) (12/29/89)

In article <1989Dec27.073432.6429@twwells.com> bill@twwells.com (T. William Wells) writes:
>I'll send it. But remember: if
>I'm answering mail, I'm not writing code.


Keep typeing. I'll wait! :-)

-- 
+----------------------------------------------------------------------+
| - Stan Voket, asv@gaboon - OR - ...uunet!hsi!stpstn!gaboon!asv       |
|               Land Line: (203) 746-4489  TELEX 4996516             - |
+----------------------------------------------------------------------+

nvk@ddsw1.MCS.COM (Norman Kohn) (01/05/90)

In article <1989Dec26.062006.13829@rancho.uucp> rock@rancho.uucp (Rock Kent) writes:
>>>>>> On 25 Dec 89 05:13:56 GMT, asv@gaboon.UUCP (Stan Voket) said:
>Stan>      I have a full screen /etc/issue that I'd like to display on
>Stan>      unused terminals to clear a previous user's work for
>Stan>      security and neatness. ...

If your users are well-behaved you can have logouts trap to
tput clear
which will clear the screens at logout. 
i.e., have /etc/profile include
trap "tput clear" 0

On my unix386 (uport), however, this fails if the user as invoked
newgrp.

-- 
Norman Kohn   		| ...ddsw1!nvk
Chicago, Il.		| days/ans svc: (312) 650-6840
			| eves: (312) 373-0564