public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/25607] New: debuginfod-client: paranoid federation mode
Date: Thu, 27 Feb 2020 22:08:00 -0000	[thread overview]
Message-ID: <bug-25607-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=25607

            Bug ID: 25607
           Summary: debuginfod-client: paranoid federation mode
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

It may be helpful to have a debuginfod_client option (env var? api?) that adds
a degree of paranoia to frontend debuginfod servers that simply federate out to
multiple mostly-trustworthy upstreams.  The present code simply launches the
outgoing curl requests to -all- upstream servers in $DEBUGINFOD_URLS, and the
first one that starts sending data back is selected as the winner.  The data
from the others is thrown away.

This is fine if all the servers are trustworthy, correct, etc. etc.

With a bit of extra code, we can detect some kinds of shenanigans or errors. 
One possibility is teaching the -client code to -not- choose the first upstream
server as the winner, but to wait for them all to send back a definite response
(subject to a timeout).  Then it can compare the responses from those servers
that claimed to know the buildid/$payload.  If there is a mismatch, signal a
loud error, as though there were a RAID-1 disagreement between mirrored disks.

With such checking logic in place, it is possible to proactively scan the
federated server tree by mechanically looking up all "interesting" buildids. 
It could permit the assembly of a semi-trusted tree of servers that still limit
client exposure to wrong data.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-02-27 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 22:08 fche at redhat dot com [this message]
2021-07-12 18:21 ` [Bug debuginfod/25607] " nsanci at redhat dot com
2021-07-26 18:57 ` nsanci at redhat dot com
2022-07-14 16:30 ` nsanci at redhat dot com

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=bug-25607-10460@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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).