From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Yann Dirson <yann.dirson@blade-group.com>,
Jim Broadus <jbroadus@xevo.com>
Cc: 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, 06 Apr 2020 22:06:29 +0100 [thread overview]
Message-ID: <47d3a012664b3477a953d4c06e797243218eed01.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+4=imZeFQwOUtfmD4AR=EJ_sSvqAZy_fiN6xPurTLB-cfBkLA@mail.gmail.com>
On Mon, 2020-04-06 at 22:58 +0200, Yann Dirson wrote:
> The problem motivating this patch may be the same that motivated a
> hack of mine which I never
> cleaned up for submit: at least in some early warrior versions curl
> was attempting to use cacerts
> from the host.
>
> This is a hand-edited copypaste and may not apply cleanly, but you
> should get the idea: make it
> so curl-native uses its own certs and not the host ones.
This should have been the case from 2014:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=92cad721d764ec28c3570dfe4a80847c3df19453
You can see fallout from that such as:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=754a9c31232979b3f0c28906c28191af55e96be2
where we had to fix curl in nativesdk to have the certs present.
So something odd is going on somewhere but I think OE-Core is fairly
consistent and has been for a few years.
Cheers,
Richard
prev parent reply other threads:[~2020-04-06 21:06 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
2020-04-06 20:58 ` Yann Dirson
2020-04-06 21:06 ` Richard Purdie [this message]
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=47d3a012664b3477a953d4c06e797243218eed01.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jbroadus@gmail.com \
--cc=jbroadus@xevo.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yann.dirson@blade-group.com \
/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