From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] openssl: update to 1.0.2i (CVE-2016-6304 and more)
Date: Fri, 23 Sep 2016 12:27:23 +0200 [thread overview]
Message-ID: <1474626443.7161.5.camel@intel.com> (raw)
In-Reply-To: <cover.1474619763.git.patrick.ohly@intel.com>
On Fri, 2016-09-23 at 10:38 +0200, Patrick Ohly wrote:
> Fixes several CVEs.
>
> It compiled for me okay for qemux86, but running the ptests showed a
> problem in one of the new tests. I'll investigate that further
There is one FAIL:
../util/shlib_wrap.sh ./dtlstest ../apps/server.pem ../apps/server.pem
Starting Test 0
Failed to load server certificate
Unable to create SSL_CTX pair
make[2]: Leaving directory '/usr/lib/openssl/ptest/test'
FAIL: test_dtls
That's because server.pem wasn't installed. I'll fix that.
However, ptest-runner returns with 0, i.e. success? Should it do that?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-09-23 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 8:38 [PATCH 0/1] openssl: update to 1.0.2i (CVE-2016-6304 and more) Patrick Ohly
2016-09-23 8:39 ` [PATCH 1/1] " Patrick Ohly
2016-09-23 12:01 ` Alexander Kanavin
2016-09-23 16:25 ` akuster808
2016-09-26 12:36 ` Alexander Kanavin
2016-09-23 10:27 ` Patrick Ohly [this message]
2016-09-23 12:11 ` [PATCH 0/1] " Alexander Kanavin
2016-09-23 13:19 ` Patrick Ohly
2016-09-23 14:52 ` Alexander Kanavin
2016-09-23 13:26 ` [PATCHv2] " Patrick Ohly
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=1474626443.7161.5.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.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