[CONC-52] Oracle and MariaDB API's differ in behaviour when establishing an SSL connection for a user with "REQURE SSL" Created: 2013-09-20  Updated: 2013-11-21  Resolved: 2013-11-21

Status: Closed
Project: MariaDB Connector/C
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sudhindra Bhat Assignee: Georg Richter
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Windows


 Description   

This is the original bug report.
https://mariadb.atlassian.net/browse/CONC-50

It was partially fixed in revision 86.
Now with revision 87,

mysql_ssl_set(MYSQL *mysql, const char *key, const char *cert, const char *ca, const char *capath, const char *cipher)

Neither client key,client certificate,ca-certificate is validated.Passing any file or any string as arguments successfully establishes the connection which is wrong. Am I missing something?

 Comments   
Comment by Georg Richter [ 2013-09-20 ]

Did you run cmake with -DWITH_OPENSSL=1?

Comment by Sudhindra Bhat [ 2013-09-20 ]

I ran cmake with :
-DWITH_SSL=yes -DOPENSSL_ROOT_DIR=c:\openssl\OpenSSL-Win32 -DOPENSSL_LIBRARIES=C:\openssl\OpenSSL-Win32\lib -DOPENSSL_INCLUDE_DIR=C:\openssl\OpenSSL-Win32\include\openssl

Comment by Georg Richter [ 2013-09-20 ]

you need to specify -DWITH_OPEN_SSL

From CMakeLists.txt
IF(WITH_OPENSSL)
FIND_PACKAGE(OpenSSL)
IF(OPENSSL_FOUND)
ADD_DEFINITIONS(-DHAVE_OPENSSL)
ENDIF()
ENDIF()

Generated at Thu Feb 08 03:02:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.