Re: PATCH PR30962, debuginfod

["Frank Ch. Eigler" <fche@redhat.com>]

Hi -

> OK. But I think you should add an explanation or example to "Front-end
> proxies can also elide sensitive path name components" paragraph. So
> the user is fully aware what those "sensitive path names" are. Maybe
> even add that debuginfod-find -v example so people can double check.

OK, rewrote the related text in the man page:

[...WEBAPI...]

For most queries, some custom http headers are added to the response,
providing additional metadata about the buildid-related response.  For example:

.SAMPLE
% debuginfod-find -v debuginfo /bin/ls |& grep -i x-debuginfo
x-debuginfod-size: 502024
x-debuginfod-archive: /mnt/fedora_koji_prod/koji/packages/coreutils/9.3/4.fc39/x86_64/coreutils-debuginfo-9.3-4.fc39.x86_64.rpm
x-debuginfod-file: /usr/lib/debug/usr/bin/ls-9.3-4.fc39.x86_64.debug
.ESAMPLE

.TP
X-DEBUGINFOD-SIZE
The size of the file, in bytes.  This may differ from the http Content-Length:
field (if present), due to compression in transit.

.TP
X-DEBUGINFOD-FILE
The full path name of the file related to the given buildid.

.TP
X-DEBUGINFOD-ARCHIVE
The full path name of the archive that contained the above file, if any.

[...SECURITY...]

Front-end proxies may elide sensitive path name components in
X-DEBUGINFOD-FILE/ARCHIVE response headers.  For example, using Apache
httpd's \fBmod_headers\fP, you can remove the entire directory name
prefix:

.SAMPLE
Header edit x-debuginfod-archive ".*/" ""
.ESAMPLE


- FChE






- FChE