Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dimi Tomov <dimi@tpm.dev>
To: buildroot@buildroot.org
Subject: [Buildroot] libcurl ignores default buildroot CA bundle
Date: Sat, 04 Jun 2022 19:43:35 +0300	[thread overview]
Message-ID: <cb76d24abec40b2e48d3d1dd2964b720@tpm.dev> (raw)

Hello Buildroot community,

I have a STM32MP1 target and my buildroot image has both the curl and 
ca-certificates package installed. However, curl fails to authenticate 
any https requests:


# curl https://google.com

curl: (77)  CA signer not available for verification


Do I need to do some extra buildroot configuration for libcurl to use 
the CA bundle in /etc/ssl/certs?

Thanks,

Dimi Tomov
--
Founder of TPM.dev
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-06-04 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04 16:43 Dimi Tomov [this message]
2022-06-04 18:16 ` [Buildroot] libcurl ignores default buildroot CA bundle Dimi Tomov
2022-06-05  7:24   ` Dimi Tomov
2022-06-05  8:16     ` Dimi Tomov
2022-06-05  8:32       ` Dimi Tomov
2022-06-05 10:04         ` Dimi Tomov
2022-06-05 12:49           ` Dimi Tomov

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=cb76d24abec40b2e48d3d1dd2964b720@tpm.dev \
    --to=dimi@tpm.dev \
    --cc=buildroot@buildroot.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