From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: About the dll search algorithm of dlopen (patch-r3)
Date: Fri, 26 Aug 2016 12:04:00 -0000 [thread overview]
Message-ID: <20160826120438.GT9783@calimero.vinschen.de> (raw)
In-Reply-To: <025fabf1-e22c-246c-c3d6-3d2e5560ae39@ssi-schaefer.com>
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
On Aug 25 19:48, Michael Haubenwallner wrote:
> On 08/22/2016 08:37 PM, Corinna Vinschen wrote:
> > (*) Yuk! Do we really, *really* want that? The redirection from
> > /usr/lib to /usr/bin is only done for system libs, and only because
> > otherwise we had trouble starting Cygwin from CMD or the Explorer
> > GUI "Run..." box. We can't change this without breaking everything
> > since we *do* depend on the Windows loader yet.
> >
> > However, as long as this is restricted to /usr/lib, /usr/bin, it's a
> > closed system under control of "the distro". If you extend this to
> > *any* external path ending in "lib", isn't it inherently dangerous
> > to automate this under the hood, without the application's consent?
> > Or, FWIW, the user's consent in case of LD_LIBRARY_PATH?
>
> 've split into add_lib_searchdir (), used for "/usr/lib" only.
Btw., I just noticed something interesting, independently of your patch.
Consider the file /usr/bin/cygz.dll:
- dlopen (libz.so) success
- dlopen (/usr/bin/libz.so) success
- dlopen (/usr/lib/libz.so) fails
That's pretty clear when looking through the code, but... wouldn't
it make sense to allow that? If a path is given, and the path points
to /usr/lib, search the file in /usr/bin as well?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-26 12:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 6:39 About the dll search algorithm of dlopen Michael Haubenwallner
2016-06-01 11:09 ` Corinna Vinschen
2016-06-01 14:25 ` Michael Haubenwallner
2016-06-01 20:18 ` Corinna Vinschen
2016-06-01 23:29 ` Yaakov Selkowitz
2016-08-19 16:37 ` Michael Haubenwallner
2016-08-19 16:39 ` Michael Haubenwallner
2016-08-20 19:32 ` Corinna Vinschen
2016-08-22 12:15 ` Michael Haubenwallner
2016-08-22 12:48 ` Peter Rosin
2016-08-22 13:01 ` Michael Haubenwallner
2016-08-22 16:02 ` About the dll search algorithm of dlopen (patch-r2) Michael Haubenwallner
2016-08-22 18:37 ` Corinna Vinschen
2016-08-23 8:16 ` Corinna Vinschen
2016-08-25 17:48 ` About the dll search algorithm of dlopen (patch-r3) Michael Haubenwallner
2016-08-26 10:59 ` Corinna Vinschen
2016-08-26 11:18 ` Corinna Vinschen
2016-08-26 11:49 ` Corinna Vinschen
2016-08-29 16:50 ` Michael Haubenwallner
2016-08-30 14:51 ` Corinna Vinschen
2016-08-30 15:57 ` Michael Haubenwallner
2016-08-31 18:48 ` Corinna Vinschen
2016-09-01 8:58 ` Michael Haubenwallner
2016-08-26 14:08 ` Michael Haubenwallner
2016-08-30 13:26 ` Corinna Vinschen
2016-08-26 12:04 ` Corinna Vinschen [this message]
2016-08-29 9:24 ` Michael Haubenwallner
2016-08-30 13:35 ` Corinna Vinschen
2016-08-30 16:41 ` Michael Haubenwallner
2016-08-31 18:43 ` Corinna Vinschen
2016-08-22 18:49 ` About the dll search algorithm of dlopen Corinna Vinschen
2016-08-23 8:55 ` Michael Haubenwallner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160826120438.GT9783@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).