From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
To: "Hans Åberg" <hans.aberg-1@telia.com>
Cc: "Guile bug" <bug-guile@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>,
bug-libtool@gnu.org
Subject: Re: Mac OS X .dylib not working
Date: Thu, 3 Mar 2011 21:00:03 -0600 (CST) [thread overview]
Message-ID: <alpine.GSO.2.01.1103032045000.15305@freddy.simplesystems.org> (raw)
In-Reply-To: <AA43950B-8D76-4B05-B65F-7925BF94F493@telia.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1284 bytes --]
On Thu, 3 Mar 2011, Hans Åberg wrote:
> So guile-2.0.0 using libltdl.7.dylib of libtool-2.4, can on Mac OS X
> 10.6.6 only open a dynamic library if the name of what it actually
> opens ends in .so (say by making a soft link using 'ln -s'); if it
> ends in .dylib, it cannot open it, even if the full name is given.
>
> See
> http://lists.gnu.org/archive/html/bug-guile/2011-03/msg00008.html
> http://lists.gnu.org/archive/html/guile-devel/2011-03/msg00021.html
Are you sure that libltdl from libtool-2.4 is being used? The dtruss
trace (from Michael Ellis) at
http://lists.gnu.org/archive/html/bug-guile/2011-03/msg00020.html
shows insecure accesses more like I would expect from a libtool
version suffering from CVE-2009-3736, which is very dangerous under OS
X. See
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3736
The recommended portable way to load modules is via a libtool module
.la file. It is also recommended to load modules via a full path
rather than via a search path because the search path might not be as
secure and predicable as you might like.
Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
next prev parent reply other threads:[~2011-03-04 3:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 19:32 Mac OS X .dylib not working Hans Åberg
2011-03-03 19:56 ` Michael Ellis
2011-03-04 2:59 ` Peter O'Gorman
2011-03-04 3:41 ` Michael Ellis
2011-03-04 8:59 ` Andy Wingo
2011-03-04 9:44 ` Hans Aberg
2011-03-04 18:07 ` Peter O'Gorman
2011-03-04 18:47 ` Ralf Wildenhues
2011-03-04 19:00 ` Peter O'Gorman
2011-03-05 16:16 ` Peter O'Gorman
2011-03-04 3:00 ` Bob Friesenhahn [this message]
2011-03-04 3:48 ` Michael Ellis
2011-03-04 17:04 ` Ralf Wildenhues
2011-03-04 9:47 ` Hans Aberg
-- strict thread matches above, loose matches on Subject: below --
2011-03-03 19:53 Hans Aberg
2010-02-01 14:26 Hans Aberg
2010-02-02 6:42 ` Ralf Wildenhues
2010-02-02 9:08 ` Hans Aberg
2010-02-02 14:20 ` Ken Raeburn
2010-02-02 15:48 ` Hans Aberg
2010-02-02 16:52 ` Bob Friesenhahn
2010-02-02 17:15 ` Hans Aberg
2010-02-02 18:01 ` Ludovic Courtès
2010-02-03 14:23 ` Ken Raeburn
2010-02-03 15:10 ` Ludovic Courtès
2010-02-04 12:40 ` Hans Aberg
2010-02-04 13:49 ` Peter O'Gorman
2010-02-04 15:21 ` Hans Aberg
2010-02-04 15:34 ` Peter O'Gorman
2010-02-04 16:52 ` Hans Aberg
2010-02-04 16:58 ` Hans Aberg
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.GSO.2.01.1103032045000.15305@freddy.simplesystems.org \
--to=bfriesen@simple.dallas.tx.us \
--cc=bug-guile@gnu.org \
--cc=bug-libtool@gnu.org \
--cc=hans.aberg-1@telia.com \
--cc=ludo@gnu.org \
/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).