public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Daniel Thornburgh <>,
Subject: Re: debuginfod Credential Helper RFC
Date: Thu, 28 Jul 2022 18:23:41 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Daniel,

On Tue, 2022-07-26 at 15:50 -0700, Daniel Thornburgh via Elfutils-devel 
> I'm working on a use case for debuginfod (in LLVM) that needs a
> solution
> for authentication and authorization of users when accessing source and
> debug information. I've put together a short RFC for how this might work,
> based on how git and Docker CLIs handle credentials. It should be fairly
> straightforward to implement and to generalize to new credential types.
> Please take a look; it'd be good to have a consensus on how this should
> work across interested debuginfod implementations before moving forward
> towards implementation.

I think this could work for a standalone program like debuginfod-find,
but not for a library like libdebuginfod. I would rather not have to
fork and exec from libdebuginfod. We don't really know in what state
the program is and forking a big process is not cheap. The process
might be watching its own children (like when libdebuginfod is used in
a debugger or profiler) and suddenly get unexpected sigchilds or pids
from wait.

Can't this be handled through e.g. the underlying libcurl library by
setting a proxy environment variable so the requests goes through a
local proxy that is setup to do some kind of authentication
transparently? Or by simply defining the base DEBUGINFOD_URL with ?



  reply	other threads:[~2022-07-28 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 22:50 Daniel Thornburgh
2022-07-28 16:23 ` Mark Wielaard [this message]
2022-07-28 17:47   ` Daniel Thornburgh
2022-07-29 18:58     ` Mark Wielaard
2022-07-29 21:08       ` Daniel Thornburgh
2022-08-02 20:36         ` Daniel Thornburgh
2022-08-04 17:02           ` Mark Wielaard
2022-08-04 18:04             ` Daniel Thornburgh
2022-08-08 20:41               ` Frank Ch. Eigler
2022-08-09 18:13                 ` Daniel Thornburgh

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).