[382] in athena10
Re: Larvnet design discussion
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Aug 5 16:02:10 2008
From: Greg Hudson <ghudson@MIT.EDU>
To: Timothy G Abbott <tabbott@mit.edu>
Cc: athena10@mit.edu
In-Reply-To: <alpine.DEB.1.10.0808051553590.21810@vinegar-pot.mit.edu>
Content-Type: text/plain
Date: Tue, 05 Aug 2008 16:00:55 -0400
Message-Id: <1217966455.12433.114.camel@error-messages.mit.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
On Tue, 2008-08-05 at 15:58 -0400, Timothy G Abbott wrote:
> Right, I was just thinking it would be nice to not have two different pam
> configuration packages if possible, but instead to use a single PAM
> configuration and have the larvnet PAM module read /etc/athena/rc.conf (or
> some similar file is included in debathena-cluster that programs like this
> could use to determine whether it is a public workstation or not) to check
> whether to nop. This is mostly an issue of managing complexity;
> debathena-pam-config is already our most complex configuration package,
> and it might be good to avoid making it any more complex by having it
> either build two binary packages or having two versions of it.
Conveniently, debathena-pam-config doesn't touch /etc/pam.d/gdm, which
is the file we want to modify for Larvnet integration. (Larvnet only
monitors graphical logins, not remote logins or text console logins.)
