From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Improve SSL certificate handling
Date: Thu, 26 May 2016 14:41:16 +0100 [thread overview]
Message-ID: <1464270076.19134.19.camel@linuxfoundation.org> (raw)
In-Reply-To: <1464036327-4826-1-git-send-email-otavio@ossystems.com.br>
On Mon, 2016-05-23 at 17:45 -0300, Otavio Salvador wrote:
> This patchset leverage the OpenSSL certificate handling so it works
> aligned with Debian and other generic distributions regarding where
> the certificates are stored and how they are installed.
>
> This all started when debugging why SSL certificates were not working
> properly for a customer which was using QtWebEngine. It turned out to
> be the integration which was not complete so this patch addresses it.
>
>
> Otavio Salvador (3):
> openssl: Add Shell-Script based c_rehash utility
> ca-certificates: Use c_rehash utility
> openssl: Ensure SSL certificates are stored on sysconfdir
Initial tests were ok but we've just seen:
https://autobuilder.yoctoproject.org/main/builders/nightly-oecore/build
s/792/steps/BuildImages/logs/stdio
I've not looked into it but it would seem to implicate these patches :/
Cheers,
Richard
next prev parent reply other threads:[~2016-05-26 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 20:45 [PATCH 0/3] Improve SSL certificate handling Otavio Salvador
2016-05-23 20:45 ` [PATCH 1/3] openssl: Add Shell-Script based c_rehash utility Otavio Salvador
2016-05-23 20:45 ` [PATCH 2/3] ca-certificates: Use " Otavio Salvador
2016-05-23 20:45 ` [PATCH 3/3] openssl: Ensure SSL certificates are stored on sysconfdir Otavio Salvador
2016-05-26 13:41 ` Richard Purdie [this message]
2016-05-27 9:55 ` [PATCH 0/3] Improve SSL certificate handling Otavio Salvador
2016-05-27 10:10 ` Martin Jansa
2016-05-27 10:28 ` Otavio Salvador
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=1464270076.19134.19.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.