Lockscreen

Dan Watts dwatts at ki.UUCP
Wed Oct 3 23:19:08 AEST 1990


In article <9631 at jpl-devvax.JPL.NASA.GOV> larrys at beowulf.JPL.NASA.GOV (Larry Seeley) writes:
>In article <1990Sep17.170536.27140 at midway.uchicago.edu> malagoli at oddjob.UChicago.EDU () writes:
>>This is my first posting to the network. 
>>I have developed a lockscreen utility for Irises 4D. It works
>>on my PI. I am no expert C programmer, so I would appreciate
>>receiving comments and/or revised versions of this program.
>Works great for me too!  Very nice!
>Possible minor problem if a user can rlogin into the PI.  Only one [lockscreen]
>process at a time is active.  If a remote user starts [lockscreen], then it
>seizes the monitor display.  (If a [lockscreen] process was already running, it
>is killed.)  Now to unlock the screen you need the remote user's password.
>(This also means any valid remote user can unlock the screen.)



I got a lockscreen program eariler this year from someone at SGI.  I
made some modifications to it to avoid the problem you mention of
letting remote users lock the screen.  I added an open to /dev/console
for Read/Write access.  On my system, only the currently logged in local
user can do that.  I also added the ability for "root" to always be able
to unlock the screen in addition to the user that locked it up.  Works
great for me.


-- 
#####################################################################
# CompuServe: >INTERNET:uunet.UU.NET!ki!dwatts    Dan Watts         #
# UUCP      : ...!{uunet | wgc386}!ki!dwatts      Ki Research, Inc. #
############### New Dimensions In Network Connectivity ##############



More information about the Comp.sys.sgi mailing list