From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83652 invoked by alias); 27 Feb 2020 22:08:53 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 83390 invoked by uid 48); 27 Feb 2020 22:08:41 -0000 From: "fche at redhat dot com" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/25607] New: debuginfod-client: paranoid federation mode Date: Thu, 27 Feb 2020 22:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: debuginfod X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2020-q1/txt/msg00158.txt https://sourceware.org/bugzilla/show_bug.cgi?id=3D25607 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 a= dds a degree of paranoia to frontend debuginfod servers that simply federate ou= t to multiple mostly-trustworthy upstreams. The present code simply launches the outgoing curl requests to -all- upstream servers in $DEBUGINFOD_URLS, and t= he 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= .=20 One possibility is teaching the -client code to -not- choose the first upst= ream server as the winner, but to wait for them all to send back a definite resp= onse (subject to a timeout). Then it can compare the responses from those serve= rs 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 dis= ks. With such checking logic in place, it is possible to proactively scan the federated server tree by mechanically looking up all "interesting" buildids= .=20 It could permit the assembly of a semi-trusted tree of servers that still l= imit client exposure to wrong data. --=20 You are receiving this mail because: You are on the CC list for the bug.