openssl/include, branch OpenSSL_1_1_1oTLS/SSL and crypto library.http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1o2022-05-03T13:41:15ZPrepare for 1.1.1o release2022-05-03T13:41:15ZMatt Caswellmatt@openssl.org2022-05-03T13:41:15Zurn:sha1:ca2e0784d2c38edcefd5d68028f4d954bd8faddb
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Release: yes
Update copyright year2022-05-03T12:38:37ZMatt Caswellmatt@openssl.org2022-05-03T10:54:12Zurn:sha1:b5b37553bcf9b90a5be5d8ed573b377d1766bd95
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Release: yes
Prepare for 1.1.1o-dev2022-03-15T14:37:56ZMatt Caswellmatt@openssl.org2022-03-15T14:37:56Zurn:sha1:60f3fa75945d97ec6f008424d2c5b6b4165fc152
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Prepare for 1.1.1n release2022-03-15T14:37:47ZMatt Caswellmatt@openssl.org2022-03-15T14:37:47Zurn:sha1:d82e959e621a3d597f1e0d50ff8c2d8b96915fd7
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Update copyright year2022-03-15T13:57:22ZMatt Caswellmatt@openssl.org2022-03-15T13:57:22Zurn:sha1:0c5bc96fb7f5f6a5f1ac3fa7709091ce463e510d
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
Prevent crash with engine using different openssl runtime2022-02-09T16:07:58ZBernd Edlingerbernd.edlinger@hotmail.de2021-11-22T20:50:04Zurn:sha1:38ac4415a9cc4cca307c866e5fc548b889fe2bb6
This problem happens usually because an application
links libcrypto and/or libssl statically which
installs an atexit handler, but later an engine using
a shared instance of libcrypto is installed.
The problem is in simple words that both instances
of libcrypto have an atexit handler installed,
but both are unable to coordinate with each other,
which causes a crash, typically a use-after-free
in the engine's destroy function.
Work around that by preventing the engine's
libcrypto to install the atexit handler.
This may result in a small memory leak, but that
memory is still reachable.
Fixes #15898
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/17541)
Fix builds with DJGPP2022-02-04T07:53:04ZJuan Manuel Guerrerojuan.guerrero@gmx.de2022-02-01T23:41:02Zurn:sha1:b728ac98f23d7b32959ca26f1a40e843b7b969a3
CLA: trivial
To get the master branch compiled with DJGPP some minor
adjustments are required. They will have no impact on any other ports.
The DJGPP port uses the Watt-32 library to provide the required network
functionality and some of its headers need to be included.
Neither DJGPP nor the Watt-32 library provide in_addr_t thus it must be
provided as it is done for OPENSSL_SYS_WINDOWS in crypto/bio/b_addr.c.
In the DJGPP section of include/internal/sockets.h the following Watt-32
headers must be added:
- arpa/inet.h: to provide declaration of inet_ntoa required in crypto/bio/b_addr.c
- netinet/tcp.h: to provide defintion of TCP_NODELAY required in crypto/bio/b_sock2.c
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/17623)
(cherry picked from commit b9b211fcb6b9068ef1d8729a4971fbe693fd2cde)
Update troublesome copyright years of auto-generated files to 20222022-01-04T21:15:57ZDr. David von OheimbDavid.von.Oheimb@siemens.com2022-01-03T12:40:55Zurn:sha1:692520a1fede55001dbce23618f992b4042ebbae
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/17401)
Prepare for 1.1.1n-dev2021-12-14T15:45:09ZMatt Caswellmatt@openssl.org2021-12-14T15:45:09Zurn:sha1:e9dc49c009a34b429d6dddcbb1813efa561481c7
Reviewed-by: Richard Levitte <levitte@openssl.org>
Prepare for 1.1.1m release2021-12-14T15:45:01ZMatt Caswellmatt@openssl.org2021-12-14T15:45:01Zurn:sha1:ac3cef223a4c61d6bee34527b6d4c8c6432494a7
Reviewed-by: Richard Levitte <levitte@openssl.org>