Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Jan 2013 12:10:10 +0100
From:      Fabian Keil <freebsd-listen@fabiankeil.de>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        Andrey Zonov <zont@FreeBSD.org>, svn-src-all@freebsd.org, Andriy Gapon <avg@freebsd.org>
Subject:   Re: bin/174831: geli segfaults with the new locked memory limit default
Message-ID:  <20130118121010.6ebba26e@fabiankeil.de>
In-Reply-To: <20130118101408.GW2522@kib.kiev.ua>
References:  <201301141058.r0EAwK4q044423@svn.freebsd.org> <20130114122640.152cb041@fabiankeil.de> <50F4464A.7000903@FreeBSD.org> <20130114200914.7f3272d2@fabiankeil.de> <50F5AB7B.6090903@FreeBSD.org> <20130115212014.GD2522@kib.kiev.ua> <20130117150022.24373166@fabiankeil.de> <50F91AFC.2050904@FreeBSD.org> <20130118101408.GW2522@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/zr1jihnNlxj/MPYmnC6UQVQ
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Konstantin Belousov <kostikbel@gmail.com> wrote:

> On Fri, Jan 18, 2013 at 01:50:52PM +0400, Andrey Zonov wrote:
> > The code that you copy/pasted is under HAVE_BROKEN_MLOCK.
> >=20
> > The code that is executed on my machine is:
> >=20
> > gnupg-1.4.13/util/secmem.c:
> > 167 #else
> > 168     err =3D mlock( p, n );
> > 169     if( err && errno )
> > 170         err =3D errno;
> > 171 #endif
> >=20
> > and it works without errors.
> >=20
> > I do not have HAVE_BROKEN_MLOCK in my config.h:
> >=20
> > /usr/ports/security/gnupg1/work/gnupg-1.4.13/config.h:/* #undef
> > HAVE_BROKEN_MLOCK */
> >=20
> > Try to recompile gnupg and check whether HAVE_BROKEN_MLOCK is defined.

I already tried that but still get the HAVE_BROKEN_MLOCK code path
which makes sense given that mlock() currently doesn't seem to work
on my system.

> FWIW, I use gnupg2 and it stopped complaining about 'using insecure memor=
y'
> without recompilation.

Interesting, I guess there's something wrong with my system then.
I may try to track the problem down in the future, but as I don't
really need mlock() for gpg it's not particular high on my list.

Fabian

--Sig_/zr1jihnNlxj/MPYmnC6UQVQ
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlD5LZYACgkQBYqIVf93VJ3ZTwCgmj6AKo0jJDd/fLnjCVEpCBGu
WzIAnRmIKRSiCBm+8y/vXg4DAaF3h9Xj
=W32U
-----END PGP SIGNATURE-----

--Sig_/zr1jihnNlxj/MPYmnC6UQVQ--



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