mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-30 18:41:56 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/extra/wolfssl/user_settings.h.in

62 lines
1.4 KiB
C
Raw Normal View History

Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have *exactly* the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)
2019-06-04 17:11:42 +02:00
#ifndef WOLFSSL_USER_SETTINGS_H
#define WOLFSSL_USER_SETTINGS_H
#define HAVE_CRL
MDEV-27373 wolfSSL 5.1.1 - compile wolfcrypt with kdf.c, to avoid undefined symbols in tls13.c - define WOLFSSL_HAVE_ERROR_QUEUE to avoid endless loop SSL_get_error - Do not use SSL_CTX_set_tmp_dh/get_dh2048, this would require additional compilation options in WolfSSL. Disable it for WolfSSL build, it works without it anyway. - fix "macro already defined" Windows warning.
2022-01-24 20:00:35 +01:00
#define WOLFSSL_HAVE_ERROR_QUEUE
Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have *exactly* the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)
2019-06-04 17:11:42 +02:00
#define WOLFSSL_MYSQL_COMPATIBLE
#define HAVE_ECC
#define ECC_TIMING_RESISTANT
#define HAVE_HASHDRBG
#define WOLFSSL_AES_DIRECT
#define WOLFSSL_SHA384
#define WOLFSSL_SHA512
#define WOLFSSL_SHA224
#define SESSION_CERT
#define KEEP_OUR_CERT
#define WOLFSSL_STATIC_RSA
Do not compile socket IO code in WolfSSL We use own IO callbacks from server code anyway.
2019-07-01 00:43:26 +02:00
#define WOLFSSL_USER_IO
Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have *exactly* the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)
2019-06-04 17:11:42 +02:00
#define WC_RSA_BLINDING
#define HAVE_TLS_EXTENSIONS
#define HAVE_AES_ECB
MDEV-22221: MariaDB with WolfSSL doesn't support AES-GCM cipher for SSL Enable AES-GCM for SSL (only). AES-GCM for encryption plugins remains disabled (aes-t fails, on some bug in GCM or CTR padding)
2021-06-09 13:27:00 +02:00
#define HAVE_AESGCM
Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have *exactly* the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)
2019-06-04 17:11:42 +02:00
#define WOLFSSL_AES_COUNTER
#define NO_WOLFSSL_STUB
#define OPENSSL_ALL
Remove WolfSSL workaround for old version. We're already on 4.4.6
2021-06-09 12:34:23 +02:00
#define WOLFSSL_ALLOW_TLSV10
Update WolfSSL Fix WolfSSL build: - Do not build with TLSv1.0,it stopped working,at least with SChannel client - Disable a test that depends on TLSv1.0 - define FP_MAX_BITS always, to fix 32bit builds. - Increase MAX_AES_CTX_SIZE, to fix build on Linux
2020-05-05 18:10:53 +02:00
#define NO_OLD_TIMEVAL_NAME
MDEV-22221 Compile WolfSSL with TLSv1.3 support
2021-07-21 21:26:25 +02:00
/* TLSv1.3 definitions (all needed to build) */
#define WOLFSSL_TLS13
#define HAVE_HKDF
#define HAVE_TLS_EXTENSIONS
#define HAVE_SUPPORTED_CURVES
#define HAVE_FFDHE_2048
#define WC_RSA_PSS
/* End of TLSv1.3 defines */
MDEV-26092 Remove things we do not use in wolfssl Add a couple of NO_XXX prprocessor constants to wolfssl build. Looked into cmake defaults, those are set there too. Some of these are (supposedly) weak ciphers, and some just fallen out from wide use.
2021-07-28 15:43:12 +02:00
/* Features we exclude */
#define NO_DSA
#define NO_HC128
#define NO_MD4
#define NO_PSK
#define NO_RABBIT
#define NO_RC4
Update WolfSSL Fix WolfSSL build: - Do not build with TLSv1.0,it stopped working,at least with SChannel client - Disable a test that depends on TLSv1.0 - define FP_MAX_BITS always, to fix 32bit builds. - Increase MAX_AES_CTX_SIZE, to fix build on Linux
2020-05-05 18:10:53 +02:00
/*
FP_MAX_BITS is set high solely to satisfy ssl_8k_key.test
WolfSSL will use more stack space with it, with fastmath
*/
MDEV-26092 Remove things we do not use in wolfssl Add a couple of NO_XXX prprocessor constants to wolfssl build. Looked into cmake defaults, those are set there too. Some of these are (supposedly) weak ciphers, and some just fallen out from wide use.
2021-07-28 15:43:12 +02:00
#cmakedefine FP_MAX_BITS 16384
Fixes for WolfSSL 5.4.0
2022-07-25 13:27:23 +02:00
#define RSA_MAX_SIZE 8192
Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have *exactly* the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)
2019-06-04 17:11:42 +02:00
#cmakedefine WOLFSSL_AESNI
#cmakedefine USE_FAST_MATH
#cmakedefine TFM_TIMING_RESISTANT
#cmakedefine HAVE_INTEL_RDSEED
MDEV-23663 - Add HAVE_INTEL_RDRAND flag for building WolfSSL, where appropiate
2020-09-17 18:05:53 +02:00
#cmakedefine HAVE_INTEL_RDRAND
Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have *exactly* the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)
2019-06-04 17:11:42 +02:00
#cmakedefine USE_INTEL_SPEEDUP
#cmakedefine USE_FAST_MATH
#cmakedefine WOLFSSL_X86_64_BUILD
Fixes for WolfSSL 5.4.0
2022-07-25 13:27:23 +02:00
#cmakedefine WOLFSSL_SP_MATH_ALL
Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have *exactly* the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)
2019-06-04 17:11:42 +02:00
#endif /* WOLFSSL_USER_SETTINGS_H */
Reference in a new issue Copy permalink