From: "Frank Ch. Eigler" <fche@redhat.com>
To: Magne Hov <mhov@undo.io>
Cc: elfutils-devel@sourceware.org
Subject: Re: Specifying CA certificates for libdebuginfod
Date: Fri, 28 May 2021 14:31:10 -0400 [thread overview]
Message-ID: <20210528183110.GB15224@redhat.com> (raw)
In-Reply-To: <5sr1hqwyjy.fsf@undo.io>
Hi -
On Fri, May 28, 2021 at 06:36:17PM +0100, Magne Hov via Elfutils-devel wrote:
> [...]
> Other components that my application uses already have ways of
> specifying a certificate bundle. [...]
> There is also an option of recognising CURL_CA_BUNDLE as that
> environment variable is already established by the curl tool, but it
> could also be good to keep the name separate to libdebuginfod.
Sure; I have no strong opinion on this. ISTM of no particular
advantage to invent a debuginfod-oriented env var for this,
as opposed to reusing "CURL_CA_BUNDLE" (but not "SSL_CERT_DIR"
or "SSL_CERT_FILE", right?).
- FChE
next prev parent reply other threads:[~2021-05-28 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 17:36 Magne Hov
2021-05-28 18:31 ` Frank Ch. Eigler [this message]
2021-07-12 16:16 ` Magne Hov
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=20210528183110.GB15224@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mhov@undo.io \
/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).