From: Ryan Goldberg <rgoldber@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>, elfutils-devel@sourceware.org
Subject: Re: [patch git] PR28284 - debuginfod x-debuginfod* header processing
Date: Tue, 6 Sep 2022 12:42:36 -0400 [thread overview]
Message-ID: <CAE8aAoonUm4o8To_qZM_GXZZzkemX0gCMxKAGop8Qc1u2vzKfg@mail.gmail.com> (raw)
In-Reply-To: <20220906160547.GE13250@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Hi all,
> Well, dunno, can't speak for we all. :-) For debugging purposes (which
> is what DEBUGINFOD_VERBOSE is), we could print all headers that come
> in, from any server we're connecting to. For API / human-friendly
> use, limiting to x-debuginfod* ones from the winning server seems more
> useful. (I hope we don't have to rethink again once the signature
> contents start coming down that pipe too - hope they're not too long.)
>
Just to add in here about the signature lengths, the maximum allowed
signature size is 1024B but most I've come across seem to be closer to
~250B. Something like
X-DEBUGINFOD-IMASIGNATURE:
030204262a64fc00806dd514e73e3008c3a357b93193c7e654aab193e3f72404132c9c103b7f9eb73a9a333f57ac38cba636fc3d00b5d7d5bc6ca755c4f5a1ec6c77620b2692807495b7519086372b0f81050b9f675ac3fd03da95bcd20bd21ba995804a082e99b39e2e37029190c56c6874fd19b5e668e52c0d8d3b2b79ceca26c52a3aab4ec6e483
Ryan
next prev parent reply other threads:[~2022-09-06 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 0:13 Frank Ch. Eigler
2022-09-06 15:49 ` Mark Wielaard
2022-09-06 16:05 ` Frank Ch. Eigler
2022-09-06 16:42 ` Ryan Goldberg [this message]
2022-09-08 11:42 ` Mark Wielaard
2022-09-08 13:45 ` Frank Ch. Eigler
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=CAE8aAoonUm4o8To_qZM_GXZZzkemX0gCMxKAGop8Qc1u2vzKfg@mail.gmail.com \
--to=rgoldber@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
--cc=mark@klomp.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).