Very Computer

Hi, all :)

I'd like to restrict a few users from logging into a specific tty.  
For example, let's say I want to prevent a user "foo" from logging into
tty02.  I know that I can add a few lines in the .kshrc file of "foo" to
do that, but I'd like to have more "user-proof" solution.  Could "login"
itself do this type of screening?  Please, help~

Big thanks in advance!

Steven Najera's CPU sent forth this bytestream:
| Hi, all :)
|
| I'd like to restrict a few users from logging into a specific tty.  
| For example, let's say I want to prevent a user "foo" from logging into
| tty02.  I know that I can add a few lines in the .kshrc file of "foo" to
| do that, but I'd like to have more "user-proof" solution.  Could "login"
| itself do this type of screening?  Please, help~

Do it in /etc/profile.  The users can't muck with that file.

--

:
############################################################################
###        (c) 1995 Lone Star Software Corp. ALL RIGHTS RESERVED         ###
###    This script must be added to the *BEGINNING* of '/etc/profile'    ###
###           Restricts login on modem port to selected users.           ###
############################################################################
MODEM_TRAP="Y" # sh & ksh
if [ "$MODEM_TRAP" = "Y" ]
then
  trap '' 2
  Printer="lp -dlaser"  
  LOG="/tmp/modem$$"
  LOGNAME="`logname`"
  case `tty` in
       /dev/tty2A) case $LOGNAME in
                   mike) # Allow mike to login at the Modem tty2A
                         echo "=================================="  > $LOG ;
                         echo "  ***  Modem Login OK       ***"    >> $LOG ;
                         echo "==================================" >> $LOG ;
                         echo "Date: `date`"                       >> $LOG ;
                         echo "ID: $LOGNAME"                       >> $LOG ;
                         echo "TTY: `tty`"                         >> $LOG ;
                         echo "==================================" >> $LOG ;
                         cat $LOG | mail -s "Modem Login_OK" root ;
                         cat $LOG | $Printer ;                      
                         rm -f $LOG ;;
                      *) # No one else gets in.
                         echo "=================================="  > $LOG ;
                         echo "  ***  MODEM LOGIN ATTEMPT  ***"    >> $LOG ;
                         echo "==================================" >> $LOG ;
                         echo "Date: `date`"                       >> $LOG ;
                         echo "ID: $LOGNAME"                       >> $LOG ;
                         echo "TTY: `tty`"                         >> $LOG ;
                         echo "==================================" >> $LOG ;
                         cat $LOG | mail -s "MODEM_ATTEMPT" root mike ;
                         cat $LOG | $Printer ;                      
                         kill -9 $$ ;      
                         exec /bin/true ;;
               esac ;;
  esac
fi

Hope this helps,
Jeff Hyman, HBW
                                .--.
__________________________  .-. |  |  __________________________________

 Cactus International, Inc. | |_|  | | | Sales:   (800) LONE-TAR
 13987 W. Annapolis Ct.  _  |___   |_| | Support: (301) 829-1622
 Mt. Airy, MD 21771    _| ~-    |   ___| Fax:     (301) 829-1623
 Jeffrey Hyman         \,  _}   |  |     FTP:     ftp.cactus.com
 CompuServe: 74710,2627  \(     |  |     WWW:     http://www.cactus.com
------------------------------- |  | -----------------------------------
                                |  |

+Hi, all :)
+
+I'd like to restrict a few users from logging into a specific tty.  
+For example, let's say I want to prevent a user "foo" from logging into
+tty02.  I know that I can add a few lines in the .kshrc file of "foo" to
+do that, but I'd like to have more "user-proof" solution.  Could "login"
+itself do this type of screening?  Please, help~

     You could add tty02 to /etc/dialups and assign the user's shell a password
in /etc/d_passwd.  Then they (and anyone else with that shell) would need to
give the password in order to log in on that tty.  To avoid annoying anyone
else with the same shell, link the user's shell to a different name and use
that in d_passwd.
     The problem with trying to restrict users with code in .profile,
/etc/profile, etc. is that hitting the interrupt key at the right moment during
login will abort the sourcing of those files.

        John
--

 +Hi, all :)
 +
 +I'd like to restrict a few users from logging into a specific tty.  
 +For example, let's say I want to prevent a user "foo" from logging into
 +tty02.  I know that I can add a few lines in the .kshrc file of "foo" to
 +do that, but I'd like to have more "user-proof" solution.  Could "login"
 +itself do this type of screening?  Please, help~

Go and snag tcp wrappers and then read up on the hosts_access man page.

--

Keeper of the Alberta B5 Mailing List|for 2048/0D2E3955 5F E1 D1 38 2A C9 46 53

"The stupider it looks, the more important it probably is." -- J.R. 'Bob' Dobbs