From: Mike Frysinger <vapier@gentoo.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: linux-man@vger.kernel.org, alx.manpages@gmail.com
Subject: Re: [PATCH] ldd: Do not recommend binutils as the safer option
Date: Mon, 16 Oct 2023 16:32:02 +0545 [thread overview]
Message-ID: <ZS0UpvcYc/0RgdkG@vapier> (raw)
In-Reply-To: <20231016061923.105814-1-siddhesh@gotplt.org>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
On 16 Oct 2023 02:19, Siddhesh Poyarekar wrote:
> The binutils security policy[1] states that diagnostic tools should not
> be expected to be safe without sandboxing, so it doesn't make sense to
> recommend it as the alternative to ldd, especially since it is not a
> drop-in replacement. Recommend sandboxing instead, since that is in
> fact the safest known way at the moment to deal with untrusted binaries.
fwiw, this is one reason why i wrote `lddtree` (although the primary reason
was cross-compiling and separate-root dirs). it's part of the pax-utils
project that's available in most distros now.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-16 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 6:19 [PATCH] ldd: Do not recommend binutils as the safer option Siddhesh Poyarekar
2023-10-16 10:08 ` Alejandro Colomar
2023-10-16 13:28 ` Siddhesh Poyarekar
2023-10-16 13:33 ` Alejandro Colomar
2023-10-16 13:46 ` Siddhesh Poyarekar
2023-10-17 18:19 ` Adhemerval Zanella Netto
2023-10-16 10:47 ` Mike Frysinger [this message]
2023-10-16 11:22 ` Alejandro Colomar
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=ZS0UpvcYc/0RgdkG@vapier \
--to=vapier@gentoo.org \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=siddhesh@gotplt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.