From: Tim Orling <timothy.t.orling@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-perl][PATCH 2/3] libio-socket-ssl-perl: upgrade from 2.052 -> 2.054
Date: Sat, 27 Jan 2018 01:29:02 -0800 [thread overview]
Message-ID: <20180127092903.17475-2-timothy.t.orling@linux.intel.com> (raw)
In-Reply-To: <20180127092903.17475-1-timothy.t.orling@linux.intel.com>
Changes:
2.054 2018/01/22
- added missing test certificates to MANIFEST
2.053 2018/01/21
- small behavior fixes
- if SSL_fingerprint is used and matches don't check for OCSP
- Utils::CERT_create - small fixes to properly specific purpose, ability to
use predefined complex purpose but disable some features
- update PublicSuffix
- updates for documentation, especially regarding pitfalls with forking or using
non-blocking sockets. Spelling fixes.
- test fixes and improvements
- stability improvements for live tests
- regenerate certificate in certs/ and make sure they are limited to the
correct purpose. Checkin program used to generate certificates.
- adjust tests since certificates have changed and some tests used
certificates intended for client authentication as server certificates,
which now no longer works
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
---
...{libio-socket-ssl-perl_2.052.bb => libio-socket-ssl-perl_2.054.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-perl/recipes-perl/libio/{libio-socket-ssl-perl_2.052.bb => libio-socket-ssl-perl_2.054.bb} (91%)
diff --git a/meta-perl/recipes-perl/libio/libio-socket-ssl-perl_2.052.bb b/meta-perl/recipes-perl/libio/libio-socket-ssl-perl_2.054.bb
similarity index 91%
rename from meta-perl/recipes-perl/libio/libio-socket-ssl-perl_2.052.bb
rename to meta-perl/recipes-perl/libio/libio-socket-ssl-perl_2.054.bb
index e4fc49344..ea78bc4e0 100644
--- a/meta-perl/recipes-perl/libio/libio-socket-ssl-perl_2.052.bb
+++ b/meta-perl/recipes-perl/libio/libio-socket-ssl-perl_2.054.bb
@@ -22,8 +22,8 @@ RDEPENDS_${PN} += "\
SRC_URI = "http://search.cpan.org/CPAN/authors/id/S/SU/SULLR/IO-Socket-SSL-${PV}.tar.gz \
file://run-ptest \
"
-SRC_URI[md5sum] = "26c9bcdfb4ba8763ef89264f21326a48"
-SRC_URI[sha256sum] = "e4897a9b17cb18a3c44aa683980d52cef534cdfcb8063d6877c879bfa2f26673"
+SRC_URI[md5sum] = "e1b412e28d107c716e7ca637e2b7f8bd"
+SRC_URI[sha256sum] = "02ea04e9a336a7d3ca9aa604c0c5b5aaf3efa513cefecfc73cc79ceeb5131e4b"
S = "${WORKDIR}/IO-Socket-SSL-${PV}"
--
2.13.6
next prev parent reply other threads:[~2018-01-27 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 9:29 [meta-perl][PATCH 1/3] libencode-perl: upgrade 2.83 -> 2.94 Tim Orling
2018-01-27 9:29 ` Tim Orling [this message]
2018-01-27 9:29 ` [meta-perl][PATCH 3/3] libmime-types-perl: upgrade 2.14 -> 2.17 Tim Orling
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=20180127092903.17475-2-timothy.t.orling@linux.intel.com \
--to=timothy.t.orling@linux.intel.com \
--cc=openembedded-devel@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