X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Subject: NSS and PAM
From: Jerome Haltom <jhaltom AT isillc DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Mon, 19 Nov 2007 10:18:25 -0600
Message-Id: <1195489105.19922.2.camel@station-1.ad.isillc.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.21.2
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

I was wondering what the potential for providing a NSS and PAM
implementation which used the built in Windows account base by default
would be.

Basically it would remove manual generation of /etc/passwd
and /etc/group. Apps which queryed for these values would just get the
right things made up on the fly. In my case, this means domain users.

I'd imagine you would map local users to 'username' and domain users to
'DOM\username' or some such, which is basically what Winbind ends up
doing on Linux.

Authentication using PAM would simply remove a lot of issues.

-- 
Jerome Haltom <jhaltom AT isillc DOT com>
Institution Solutions LLC
	

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/