owl-users - Re: crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / NEWS community lists Wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Sat, 20 May 2006 16:53:11 +0400
From: "Dmitry V. Levin" <ldv@...linux.org>
To: owl-users@...ts.openwall.com
Subject: Re: crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems

Hi,
On Fri, May 19, 2006 at 11:08:38PM -0600, Vincent Danen wrote:
[...]
> crypt-entry.c:74: warning: function declaration isn't a prototype
> crypt-entry.c:142: error: 'fcrypt' aliased to undefined symbol 'crypt'
[...]
> Any ideas on what might be causing the problem?

Modern gcc requires to make symbol definition available for weak_alias.

In unpatched glibc, "crypt" symbol is defined in the same file
(crypt-entry.c) as "fcrypt" alias.
In crypt_blowfish (up to 1.0.1), the "crypt" symbol is defined in wrapper.c
as weak alias to "__crypt".  Obvious fix would be to move "fcrypt"
definition from crypt-entry.c to wrapper.c

-- 
ldv

[ CONTENT OF TYPE application/pgp-signature SKIPPED ]