prepare for 5.6.3
This commit is contained in:
parent
58c1c0c31b
commit
72536e0e10
@ -28,13 +28,13 @@ if("${CMAKE_SOURCE_DIR}" STREQUAL "${CMAKE_BINARY_DIR}")
|
||||
You must delete them, or cmake will refuse to work.")
|
||||
endif()
|
||||
|
||||
project(wolfssl VERSION 5.6.2 LANGUAGES C ASM)
|
||||
project(wolfssl VERSION 5.6.3 LANGUAGES C ASM)
|
||||
|
||||
# shared library versioning
|
||||
# increment if interfaces have been added, removed or changed
|
||||
set(LIBTOOL_CURRENT 40)
|
||||
# increment if source code has changed set to zero if current is incremented
|
||||
set(LIBTOOL_REVISION 0)
|
||||
set(LIBTOOL_REVISION 1)
|
||||
# increment if interfaces have been added set to zero if interfaces have been
|
||||
# removed or changed
|
||||
set(LIBTOOL_AGE 5)
|
||||
|
@ -1,3 +1,10 @@
|
||||
# wolfSSL Release 5.6.3 (Jun 13, 2023)
|
||||
|
||||
Release 5.6.3 of wolfSSL embedded TLS has 2 bug fixes
|
||||
* Fix for setting the atomic macro options introduced in release 5.6.2. This issue affects GNU gcc autoconf builds. The fix resolves a potential mismatch of the generated macros defined in options.h file and the macros used when the wolfSSL library is compiled. In version 5.6.2 this mismatch could result in unstable runtime behavior.
|
||||
* Fix for invalid suffix error with Windows build using the macro GCM_TABLE_4BIT.
|
||||
|
||||
|
||||
# wolfSSL Release 5.6.2 (Jun 09, 2023)
|
||||
|
||||
Release 5.6.2 has been developed according to wolfSSL's development and QA process (see link below) and successfully passed the quality criteria.
|
||||
|
@ -51,8 +51,8 @@ END
|
||||
//
|
||||
|
||||
VS_VERSION_INFO VERSIONINFO
|
||||
FILEVERSION 5,6,2,0
|
||||
PRODUCTVERSION 5,6,2,0
|
||||
FILEVERSION 5,6,3,0
|
||||
PRODUCTVERSION 5,6,3,0
|
||||
FILEFLAGSMASK 0x3fL
|
||||
#ifdef _DEBUG
|
||||
FILEFLAGS 0x1L
|
||||
@ -69,12 +69,12 @@ BEGIN
|
||||
BEGIN
|
||||
VALUE "CompanyName", "wolfSSL Inc."
|
||||
VALUE "FileDescription", "The wolfSSL FIPS embedded SSL library is a lightweight, portable, C-language-based SSL/TLS library targeted at IoT, embedded, and RTOS environments primarily because of its size, speed, and feature set."
|
||||
VALUE "FileVersion", "5.6.2.0"
|
||||
VALUE "FileVersion", "5.6.3.0"
|
||||
VALUE "InternalName", "wolfssl-fips"
|
||||
VALUE "LegalCopyright", "Copyright (C) 2022"
|
||||
VALUE "OriginalFilename", "wolfssl-fips.dll"
|
||||
VALUE "ProductName", "wolfSSL FIPS"
|
||||
VALUE "ProductVersion", "5.6.2.0"
|
||||
VALUE "ProductVersion", "5.6.3.0"
|
||||
END
|
||||
END
|
||||
BLOCK "VarFileInfo"
|
||||
|
9
README
9
README
@ -70,6 +70,15 @@ should be used for the enum name.
|
||||
|
||||
*** end Notes ***
|
||||
|
||||
# wolfSSL Release 5.6.3 (Jun 13, 2023)
|
||||
|
||||
Release 5.6.3 has been developed according to wolfSSL's development and QA process (see link below) and successfully passed the quality criteria.
|
||||
|
||||
Release 5.6.3 of wolfSSL embedded TLS has 2 bug fixes
|
||||
* Fix for setting the atomic macro options introduced in release 5.6.2. This issue affects GNU gcc autoconf builds. The fix resolves a potential mismatch of the generated macros defined in options.h file and the macros used when the wolfSSL library is compiled. In version 5.6.2 this mismatch could result in unstable runtime behavior.
|
||||
* Fix for invalid suffix error with Windows build using the macro GCM_TABLE_4BIT.
|
||||
|
||||
|
||||
# wolfSSL Release 5.6.2 (Jun 09, 2023)
|
||||
|
||||
Release 5.6.2 has been developed according to wolfSSL's development and QA process (see link below) and successfully passed the quality criteria.
|
||||
|
@ -79,6 +79,15 @@ single call hash function. Instead the name `WC_SHA`, `WC_SHA256`, `WC_SHA384` a
|
||||
`WC_SHA512` should be used for the enum name.
|
||||
|
||||
|
||||
# wolfSSL Release 5.6.3 (Jun 14, 2023)
|
||||
|
||||
Release 5.6.3 has been developed according to wolfSSL's development and QA process (see link below) and successfully passed the quality criteria.
|
||||
|
||||
Release 5.6.3 of wolfSSL embedded TLS has 2 bug fixes
|
||||
* Fix for setting the atomic macro options introduced in release 5.6.2. This issue affects GNU gcc autoconf builds. The fix resolves a potential mismatch of the generated macros defined in options.h file and the macros used when the wolfSSL library is compiled. In version 5.6.2 this mismatch could result in unstable runtime behavior.
|
||||
* Fix for invalid suffix error with Windows build using the macro GCM_TABLE_4BIT.
|
||||
|
||||
|
||||
# wolfSSL Release 5.6.2 (Jun 09, 2023)
|
||||
|
||||
Release 5.6.2 has been developed according to wolfSSL's development and QA process (see link below) and successfully passed the quality criteria.
|
||||
|
@ -7,7 +7,7 @@
|
||||
#
|
||||
AC_COPYRIGHT([Copyright (C) 2006-2020 wolfSSL Inc.])
|
||||
AC_PREREQ([2.69])
|
||||
AC_INIT([wolfssl],[5.6.2],[https://github.com/wolfssl/wolfssl/issues],[wolfssl],[https://www.wolfssl.com])
|
||||
AC_INIT([wolfssl],[5.6.3],[https://github.com/wolfssl/wolfssl/issues],[wolfssl],[https://www.wolfssl.com])
|
||||
AC_CONFIG_AUX_DIR([build-aux])
|
||||
|
||||
# The following sets CFLAGS to empty if unset on command line. We do not
|
||||
@ -48,8 +48,8 @@ AC_SUBST([WOLFSSL_CONFIG_ARGS])
|
||||
# these numbers don't always line up nicely with the library version.
|
||||
WOLFSSL_LIBRARY_VERSION_FIRST=35
|
||||
WOLFSSL_LIBRARY_VERSION_SECOND=5
|
||||
WOLFSSL_LIBRARY_VERSION_THIRD=0
|
||||
WOLFSSL_LIBRARY_VERSION=40:0:5
|
||||
WOLFSSL_LIBRARY_VERSION_THIRD=1
|
||||
WOLFSSL_LIBRARY_VERSION=40:1:5
|
||||
# | | |
|
||||
# +------+ | +---+
|
||||
# | | |
|
||||
|
BIN
wolfssl.rc
BIN
wolfssl.rc
Binary file not shown.
@ -28,8 +28,8 @@
|
||||
extern "C" {
|
||||
#endif
|
||||
|
||||
#define LIBWOLFSSL_VERSION_STRING "5.6.2"
|
||||
#define LIBWOLFSSL_VERSION_HEX 0x05006002
|
||||
#define LIBWOLFSSL_VERSION_STRING "5.6.3"
|
||||
#define LIBWOLFSSL_VERSION_HEX 0x05006003
|
||||
|
||||
#ifdef __cplusplus
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user