From owner-freebsd-questions@FreeBSD.ORG Thu Nov 3 21:14:54 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B25216A41F; Thu, 3 Nov 2005 21:14:54 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97E6543D49; Thu, 3 Nov 2005 21:14:53 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jA3LEqDr086573; Thu, 3 Nov 2005 16:14:52 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <436A7DCC.3000306@wmptl.com> Date: Thu, 03 Nov 2005 16:14:52 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: current@freebsd.org Subject: nssswitch - anyone using nss_X ? nss/freebsd complete? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 21:14:54 -0000 Anyone using any sort of nss_X.so module? Are there any open issues with FreeBSD/amd64 and nssswitch? I've been reading a good deal of archived mailing list messages regarding development/threading issues, but to no avail have I found any definitive answer as to if nssswitch works correctly and completely under FreeBSD. Personal interest being drawn from my own issues using, configuring, and updating/compiling nss_ldap. Issues in the code, issues with making new versions, and apparently just issues all-together :( Thinking perhaps someone else out there is using without problem some sort of nss solution? Sparing one problem, current version from FreeBSD/ports/current seems to work correctly, but problem is quite an issue and potential security risk - the likes of which I am still unsure of. I have posted a few times to various mailing lists, and am a member of freebsd-questions, freebsd-current, freebsd-hackers, freebsd-amd64, and nssldap/padl.com - all to no resolution thus far. I'd ideally just like to do the wrench-work and get new(er) version of nss_ldap to compile/function properly under FreeBSD. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/