</afs/transarc.com/service/mailqs/q1/QF.0ikHJA70Bi82ASoU5o>;
Wed, 9 Nov 1994 15:47:08 -0500 (EST)
Received: from us.itd.umich.edu (stimpy.us.itd.umich.edu,
[141.211.164.7]) by po2.transarc.com (5.54/3.15) id <AA07885> for
info-afs; Wed, 9 Nov 94 15:47:02 EST
Received: from localhost by us.itd.umich.edu (8.6.9/2.2)
with SMTP id PAA07192; Wed, 9 Nov 1994 15:47:01 -0500
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: .authorize access control?
Date: Wed, 09 Nov 1994 15:47:00 -0500
From: "Jason Larke" <[EMAIL PROTECTED]>
AFS's xdm program has an access control mechanism based on a
series of files listing which pts groups are allowed which
sorts of access to the machines. In the past our site used
to use these to control who could log into our machines
without having to take people out of the password file. The
login programs we're now using don't seem to pay attention
to this mechanism, however.
Is .authorize still supported by Transarc? Is it documented
anywhere? We're using modified versions of the login
program, so I can see where the .authorize code might have
been deleted, but I'd like to be know whether removing it is
"wrong" or not.
Thanks!
+-----------------------------------------------------------------------+
|Jason Larke- [EMAIL PROTECTED] sysadmin, philosophy guy, and Rush fan |
| "Good. Bad. I'm the guy with the gun." - Ash, from Army of Darkness |
| I don't speak for anyone except you. |
+-----------------------------------------------------------------------+
