Date: Sun, 04 Oct 2009 12:07:40 -0700 From: Doug Barton <dougb@FreeBSD.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: jhell <jhell@DataIX.net>, stable@freebsd.org, Andre Albsmeier <Andre.Albsmeier@siemens.com> Subject: Re: security.bsd.map_at_zero=0 problem with samba33 (including solution) Message-ID: <4AC8F27C.8070208@FreeBSD.org> In-Reply-To: <20091003215821.V26486@maildrop.int.zabbadoz.net> References: <20091003184220.GA2620@curry.mchp.siemens.de> <alpine.BSF.2.00.0910031624080.28602@dimension.5p.local> <20091003212308.GA3122@curry.mchp.siemens.de> <20091003215821.V26486@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bjoern A. Zeeb wrote: > On Sat, 3 Oct 2009, Andre Albsmeier wrote: > > Hi, > >> On Sat, 03-Oct-2009 at 16:27:32 -0400, jhell wrote: >>> On Sat, 3 Oct 2009 14:42 -0000, Andre.Albsmeier wrote: >>> >>>> FYI, >>>> >>>> after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all >>>> samba33 programmes did abort() immediately after start. The >>>> solution was to use >>>> >>>> CONFIGURE_ARGS+= --disable-pie >>>> >>>> -Andre >>>> >>> >>> To add an additional note samba33 even when not running (not enabled >>> by a rcvar) >>> also runs a tdbcleanup routine on shutdown and/or start that also does >>> abort(). >> >> Yes, every samba programme is linked with -pie per default (so >> all abort()). > > > Thanks for reporting the issue. People are aware of the problem now > and we'll try to present a solution within the next days for better > position-independent executable (PIE) handling. > > Meanwhile there are multiple solutions for people affected: > > (1) recompile the port; Just to be clear, you have to recompile the port with --disable-pie added to the CONFIGURE_ARGS in the Makefile. It would also be nice if there were a __FreeBSD_version bump for this new feature. Doug -- This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AC8F27C.8070208>