From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sourabh Hegde <hrsourabh011@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Updating trust store using update-ca-certificates
Date: Sat, 18 Feb 2023 12:19:40 +0100 [thread overview]
Message-ID: <20230218121940.7442410e@windsurf> (raw)
In-Reply-To: <CADYjeStG8bZEBprwqez+_3+n-HZ5pG9p8mBySxV+4FU7GM0r3g@mail.gmail.com>
On Fri, 17 Feb 2023 17:15:39 +0100
Sourabh Hegde <hrsourabh011@gmail.com> wrote:
> I am trying to add a custom CA to the trust store. I have copied the CA
> file to "/usr/local/share/ca-certificates/" in the rootfs_overlay and also
> has a .crt extension. Now after executing "make" the CA is not added to the
> trust store in /etc/ssl/certs/ in the target. Anyways it's installed only
> in "/usr/local/share/ca-certificates/" in the target. I thought
> "update-ca-certificates" will add this during image build.
> Can anyone please let me know what is missing here?
What makes you think update-ca-certificates is run during the build? I
don't remember Buildroot having anything that does this.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-18 11:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 16:15 [Buildroot] Updating trust store using update-ca-certificates Sourabh Hegde
2023-02-18 11:19 ` Thomas Petazzoni via buildroot [this message]
2023-02-18 12:54 ` Sourabh Hegde
2023-02-18 13:19 ` Thomas Petazzoni via buildroot
2023-02-18 13:39 ` Sourabh Hegde
2023-02-18 14:21 ` Yann E. MORIN
2023-02-18 15:32 ` Yann E. MORIN
2023-02-18 15:56 ` Sourabh Hegde
2023-02-18 17:00 ` Sourabh Hegde
2023-02-19 12:53 ` Sourabh Hegde
2023-02-19 13:17 ` Yann E. MORIN
2023-02-20 10:10 ` Sourabh Hegde
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=20230218121940.7442410e@windsurf \
--to=buildroot@buildroot.org \
--cc=hrsourabh011@gmail.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.