From owner-freebsd-security@FreeBSD.ORG Sun Mar 1 12:02:55 2009 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3B2E106578E for ; Sun, 1 Mar 2009 12:02:54 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A40138FC1B for ; Sun, 1 Mar 2009 12:02:54 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 73B2A6D43F; Sun, 1 Mar 2009 12:02:53 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 547D1844DE; Sun, 1 Mar 2009 13:02:53 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Ivan Grover References: <670f29e20902240717m49f53bfx67166c151c01384b@mail.gmail.com> <86eixnfwr2.fsf@ds4.des.no> <670f29e20902270618m23eed4acg15a8a3e7b43fe327@mail.gmail.com> <670f29e20902270810h22adc102rd9500d74208b1f11@mail.gmail.com> Date: Sun, 01 Mar 2009 13:02:53 +0100 In-Reply-To: <670f29e20902270810h22adc102rd9500d74208b1f11@mail.gmail.com> (Ivan Grover's message of "Fri, 27 Feb 2009 21:40:42 +0530") Message-ID: <86fxhxh2mq.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-security@freebsd.org Subject: Re: PAM rules inside pam.d X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2009 12:03:13 -0000 Ivan Grover writes: > I debugged pam_unix aswell, it looks like crypt function is giving > different strings for telnet and my application with same passwd > string and salt. So i think the issue could be with crypt library > linked telnet and my application. > please let me know your thoughts There's not much I can say (or think) since you still haven't told me what you upgraded *from* and *to*, but I doubt very much that there is anything wrong with crypt(). The only two possibilities I can think of are a) your application calls set_crypt_format() with an incorrect argument, or b) your application contains an alternate (incorrect) implementation of crypt(), or is linked to a library that does. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no