From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/ca-certificates: generate the bundle of certs
Date: Fri, 03 Apr 2015 10:31:04 -0300 [thread overview]
Message-ID: <551E9618.9060409@zacarias.com.ar> (raw)
In-Reply-To: <1428016146-15442-1-git-send-email-yann.morin.1998@free.fr>
On 04/02/2015 08:09 PM, Yann E. MORIN wrote:
> glib-networking wants to use the certificates bundle, not the individual
> certificates.
>
> Generating the bundle is usually done with update-ca-certificates, but
> that does not support running out-of-tree.
>
> Fortiunately, and as Gustavo put it, update-ca-certificates is jsut a
> glorified 'cat'. It is supposed to be fed a config file stating which
> certificate to add/remove to/from the bundle, otherwise nothing fancy
> (Oh, yes, running hooks after updating the bundle).
>
> Since we do not need any of this in Buidlroot, we jsut generate a bundle
> with all certificates unconditionally.
>
> Reported-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
(midori qemu-arm-vexpress with good certificate site + bad site)
(when this was missing it would report every site as bad CA when
clicking on the lock icon "the signing certificate authority is not
know" - besides the console warning).
Regards.
next prev parent reply other threads:[~2015-04-03 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 23:09 [Buildroot] [PATCH] package/ca-certificates: generate the bundle of certs Yann E. MORIN
2015-04-03 13:31 ` Gustavo Zacarias [this message]
2015-04-03 13:40 ` Thomas Petazzoni
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=551E9618.9060409@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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.