All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: linux-man@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH] ldd: Do not recommend binutils as the safer option
Date: Mon, 16 Oct 2023 15:33:11 +0200	[thread overview]
Message-ID: <ZS07lyyLzTRXO7Ta@debian> (raw)
In-Reply-To: <9af68795-52c0-f376-220c-d13d7adf622a@gotplt.org>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

Hi Siddhesh,

On Mon, Oct 16, 2023 at 09:28:39AM -0400, Siddhesh Poyarekar wrote:
> > Should we maybe keep this example, and suggest using it with sandboxing?
> > Or is it not useful anymore?
> 
> I don't see the point TBH.

The point was to add another layer of security, in case the sanboxing is
not perfect.

> I wouldn't mind if that example was replaced
> with lddtree as the alternative since it is functionally equivalent. However
> it would be a safer recommendation to put that too inside a sandbox because
> IMO you'd generally never want to run or even analyze arbitrary executables
> without proper sandboxing.

Sure, I didn't know about lddtree.  Feel free to use it.

Thanks,
Alex

P.S.:
I'm deprecating <alx.manpages@gmail.com>.  Please use <alx@kernel.org>.

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-10-16 13:33 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 [this message]
2023-10-16 13:46       ` Siddhesh Poyarekar
2023-10-17 18:19         ` Adhemerval Zanella Netto
2023-10-16 10:47 ` Mike Frysinger
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=ZS07lyyLzTRXO7Ta@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=siddhesh@gotplt.org \
    --cc=vapier@gentoo.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.