Date: Sun, 01 Mar 2009 13:02:53 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Ivan Grover <ivangrvr299@gmail.com> Cc: freebsd-security@freebsd.org Subject: Re: PAM rules inside pam.d Message-ID: <86fxhxh2mq.fsf@ds4.des.no> In-Reply-To: <670f29e20902270810h22adc102rd9500d74208b1f11@mail.gmail.com> (Ivan Grover's message of "Fri, 27 Feb 2009 21:40:42 %2B0530") References: <670f29e20902240717m49f53bfx67166c151c01384b@mail.gmail.com> <86eixnfwr2.fsf@ds4.des.no> <670f29e20902270618m23eed4acg15a8a3e7b43fe327@mail.gmail.com> <670f29e20902270810h22adc102rd9500d74208b1f11@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Grover <ivangrvr299@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86fxhxh2mq.fsf>