From owner-freebsd-hackers  Wed Dec  6 16: 6:49 2000
From owner-freebsd-hackers@FreeBSD.ORG  Wed Dec  6 16:06:47 2000
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailhub.iastate.edu (mailhub.iastate.edu [129.186.1.102])
	by hub.freebsd.org (Postfix) with ESMTP id C7F7E37B400
	for <freebsd-hackers@freebsd.org>; Wed,  6 Dec 2000 16:06:46 -0800 (PST)
Received: from iastate.edu ([129.186.232.231])
	by mailhub.iastate.edu (8.9.3/8.9.3) with ESMTP id SAA18830
	for <freebsd-hackers@freebsd.org>; Wed, 6 Dec 2000 18:06:46 -0600
Sender: ccsanady@iastate.edu
Message-ID: <3A2ED495.397B46A3@iastate.edu>
Date: Thu, 07 Dec 2000 00:06:46 +0000
From: Chris <ccsanady@iastate.edu>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: PAM issues..
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi, I have been writing a PAM module to do Kerberos 5 and AFS stuff, and
have run across a couple of problems.

First of all, the simple one. :)  How do you set or modify an
environment
variable? Neither setenv, pam_misc_setenv, or pam_putenv seem to be
work.
From what I gather from the pam_ssh module, there may be issues with
where
the environment is located, but they are not terribly clear to me.

The next is pam_setcred().  I've noticed that this is not actually
called
from login/etc, so it doesn't do much good.  Is this intentional?  Not
that it matters much, for anything other than compatibility with other
modules.

Also, are there any thoughts on session support?  It seems like it would
be pretty trivial to have login hang around to execute these hooks. 
Most
any other method of logging in (ssh, xdm, etc) already provides a
context
to do this from.  What is the thought on keeping login around?

I would be willing to try to fix the last two, but I'm not sure what to
do with the first.  Any ideas as to that problem would be welcome.

Chris


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message