Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120824000209.74ab2a3b@sibserver.ru>
Date: Fri, 24 Aug 2012 00:02:09 +0800
From: orc <orc@...server.ru>
To: musl@...ts.openwall.com
Subject: Re: ldso: dlclose.

On Thu, 23 Aug 2012 08:48:16 -0400
Rich Felker <dalias@...ifal.cx> wrote:

> Anyway, unless the issue is fixed in binutils so that the vast
> majority of libraries are marked non-unloadable, I don't see anything
> we can do in musl. "glibc does it that way too" is not an excuse for
> adding unsafe/non-robust behavior to musl.
> 
> Rich

The whole dlopen/dlclose/dlsym functions family are 'harmful': even if
we want static linking, application will still rely on them and fail
invisibly, creating more headaches.
I think better leave dlclose() in it's current state now. It will always
'success', nobody will care.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.