Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: (1) Login time (2) TT: access
Message-ID: <8318@ucbvax.ARPA>
Date: Wed, 19-Jun-85 16:40:25 EDT
Article-I.D.: ucbvax.8318
Posted: Wed Jun 19 16:40:25 1985
Date-Received: Thu, 20-Jun-85 09:20:15 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 22

From: Richard Garland <OC.GARLAND@CU20B.ARPA>

Question 1 - last Login time:
	Last login time is kept in SYSUAF.DAT and you need SYSPRV to
	read it.  In principle you could make it WORLD:READ but then
	people could read stuff and try to back-translate passwords.
	I would say write a short privileged program to read or display
	it for yourself.

Question 2 - Spawning Kermit from privileged image.
	The main process which has the privilege to allocate the lines
	should turn off the privilege after allocating the
	line etc. and before spawning Kermit.  In general you should
	always turn privilege on just before you need them and turn them 
	off again right after.  In version 4.0 you don't need SETPRV to do 
	this and it's much safer.  To try you stuff before giving it
	to users, SPAWN a DCL subproc, and run the job from a non-prived
	account and see if you can break things from the sub-proc.  Things
	should be OK if you turn the privs on just when you need them.

					Rg
-------