From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] openssl 1.1.1b-1
Date: Mon, 18 Mar 2019 01:57:00 -0000 [thread overview]
Message-ID: <announce.20190317203038.23107-1-yselkowitz@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* openssl-1.1.1b-1
* openssl-perl-1.1.1b-1
* libssl1.1-1.1.1b-1
* libssl-devel-1.1.1b-1
* libssl1.0-1.0.2r-2
* libssl1.0-devel-1.0.2r-2
The OpenSSL toolkit provides support for secure communications between
machines. OpenSSL includes a certificate management tool and shared
libraries which provide various cryptographic algorithms and protocols.
This is a major update to the latest upstream release, which includes
the following changes:
* 1.1 changes the API to make data structures opaque to applications. By
now, most active projects have updated their code for 1.1 compatibility,
which is why we waited until now to switch to the 1.1 branch. If you
have code that still needs to be ported, the following may be of help:
https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes
* Most of Fedora's patchset has been applied.
* The /usr/ssl directory has been replaced by /etc/pki/tls. In that
directory, there are two separate config files, openssl.cnf for 1.1 and
openssl10.conf for 1.0.
* Due to this change, ca-certificates 2.26 is required.
* Support for system crypto policies has been enabled.
* The upstream location of engines has changed for 1.1, and 1.0 has moved
for consistency. This should be mostly transparent, except for users which
have built their own engines, which should now be rebuilt anyway.
* The 1.0 library is still provided for binary compatibility with existing
packages.
* For those (hopefully rare) packages which are not compatible with 1.1
and for which such a patch cannot be found, a -devel package for 1.0 is
also available. In order to use it, when pkg-config is used to find
openssl, you must add /usr/lib/openssl-1.0/lib/pkgconfig to PKG_CONFIG_PATH,
otherwise you must add /usr/lib/openssl-1.0/include to your includepath and
/usr/lib/openssl-1.0/lib to your libpath. (The exact method will depend on
the package.)
However, please note that 1.0 will only be supported with security fixes
for the remainder of the calendar year, so now is the time to rebuild
your code and packages with, or port them to, 1.1.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2019-03-18 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 1:57 Yaakov Selkowitz [this message]
2019-03-20 18:47 ` Brian Inglis
2019-03-22 18:16 ` Yaakov Selkowitz
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=announce.20190317203038.23107-1-yselkowitz@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).