Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Jan 2010 13:33:53 -0600 (CST)
From:      Greg Rivers <gcr+freebsd-stable@tharned.org>
To:        Damian Weber <dweber@htw-saarland.de>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: strange abort with kcheckpass
Message-ID:  <alpine.BSF.2.00.1001121249130.28715@roadkill.tharned.org>
In-Reply-To: <alpine.BSF.2.00.1001121603340.74490@magritte.htw-saarland.de>
References:  <alpine.BSF.2.00.1001121603340.74490@magritte.htw-saarland.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Jan 2010, Damian Weber wrote:

> I've got a strange SIGABRT issue with kcheckpass. Of course, kcheckpass 
> is not contained in the base system, yet I write to this list since the 
> base system could be able to help with tracking this down. (kcheckpass 
> is called from a screen locker which fails to operate properly as a 
> consequence of the SIGABRT.)
>
> Normal behaviour:
> (for example with wrong password)
> $ kcheckpass
> Password:
> Authentication failure
>
> Strange behaviour here (called mybox below):
> $ kcheckpass
> Abort trap: 6
>

Have you set security.bsd.map_at_zero=0 ?  In my experience, several ports 
(eg. samba, cups, parts of kde3) depend on PIE and will not run with this 
disabled on 7.x.

References: 
http://security.freebsd.org/advisories/FreeBSD-EN-09:05.null.asc
http://lists.freebsd.org/pipermail/freebsd-stable/2009-October/052235.html

-- 
Greg Rivers



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1001121249130.28715>