public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: jbroadus@xevo.com
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Jim Broadus <jbroadus@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] curl: allow configuration of default CA bundle location
Date: Mon, 6 Apr 2020 13:35:42 -0700	[thread overview]
Message-ID: <ee3a15cb-afde-3b3f-59be-9c279313927c@xevo.com> (raw)
In-Reply-To: <3d20f00ac2d4f54f6bf4e67998df400548f0bfeb.camel@linuxfoundation.org>

On 4/6/20 5:00 AM, Richard Purdie wrote:
> On Sun, 2020-04-05 at 23:00 -0700, Jim Broadus wrote:
>> Add a CA_BUNDLE variable to set the built-in CA bundle location. By default,
>> don't set anything for curl-native since that target's sysconfdir is a
>> location in the recipe's native sysroot directory.
>>
>> Signed-off-by: Jim Broadus <jbroadus@xevo.com>
> 
> That is a huge change in behaviour with potentially quite serious side
> effects. As far as I remember we deliberately make our native utils
> self contained rather than relying on the host system (which may or may
> not have cert files).
> 
> We point at sysconfdir in the native case since we install ca-
> certificates there if I remember correctly?
> 
> Cheers,
> 
> Richard
> 

Hi Richard. Currently, I don't see the certs installed in the native 
sysroot, so maybe this was broken recently. If that was the intended 
behavior, I can look for a fix for that instead.

Thanks,
Jim


  reply	other threads:[~2020-04-06 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06  6:00 [OE-core][PATCH] curl: allow configuration of default CA bundle location Jim Broadus
2020-04-06 12:00 ` Richard Purdie
2020-04-06 20:35   ` jbroadus [this message]
2020-04-06 20:58     ` Yann Dirson
2020-04-06 21:06       ` Richard Purdie

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=ee3a15cb-afde-3b3f-59be-9c279313927c@xevo.com \
    --to=jbroadus@xevo.com \
    --cc=jbroadus@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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