Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: remove RPATH tag
Date: Mon, 17 Nov 2014 15:38:53 +0200	[thread overview]
Message-ID: <20141117133853.GH2196@tarshish> (raw)
In-Reply-To: <5469EDFC.3050208@zacarias.com.ar>

Hi Gustavo,

On Mon, Nov 17, 2014 at 09:45:48AM -0300, Gustavo Zacarias wrote:
> On 11/17/2014 09:33 AM, Baruch Siach wrote:
> > It seems that libtool decides to set rpath based on .la files we have in 
> > staging. Some of them (e.g. glib provided libs, and libnl) set either 
> > 'dependency_libs' (glib) or 'libdir' (libnl) to paths under output/build 
> > or staging. wireshark also links its own libraries (e.g. wiretap, epan) 
> > using local source tree .la files. I'm not sure how to solve this in the 
> > general case. It probably requires fixing up all these .la files.
> 
> There's a good briefing at https://wiki.debian.org/RpathIssue
> Fixing up is nice, however doing it in a good manner will require many
> autoreconfs and being proactive about it.
> Stripping RPATHs is probably a faster way out (via chrpath).
> In the end this could be considered as a build information leak, not
> terribly useful but doesn't look good either.

chrpath can indeed nullify the ELF RPATH tag, but it leaves the ELF string 
table alone. This means that the build paths information leak is still there, 
though somewhat less noticeable.

Until we find a better solution I think this patch can go in for -next.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  parent reply	other threads:[~2014-11-17 13:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 18:35 [Buildroot] [PATCH] wireshark: remove RPATH tag Baruch Siach
2014-11-05  7:15 ` Thomas Petazzoni
2014-11-05  7:22   ` Baruch Siach
2014-11-05  7:31     ` Thomas Petazzoni
2014-11-17 12:33       ` Baruch Siach
2014-11-17 12:45         ` Gustavo Zacarias
2014-11-17 13:32           ` Samuel Martin
2014-11-17 13:38           ` Baruch Siach [this message]
2015-04-04 17:59 ` Thomas Petazzoni
2015-04-05  9:05   ` Yann E. MORIN
2015-04-05  9:29     ` Thomas Petazzoni
2015-04-05 10:06       ` Yann E. MORIN

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=20141117133853.GH2196@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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