You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MySQL has the ability to have secured connections via a certificate. This is quite simple in Azure to configure. However ADODB's connect function inits-and-connects in one fell swoop, and the SSL trigger needs to happen between the two if it's not part of the my.cnf. I'd like to propose an extension to the adodb-mysqli.inc.php code:
class ADODB_mysqli extends ADOConnection { ... var $multiQuery = false; var $ssl_key = false; var $ssl_cer = false; var $ssl_ca = false; var $ssl_capath = false; var $ssl_cipher = false;
... if ($persist && PHP_VERSION > 5.2 && strncmp($argHostname,'p:',2) != 0) $argHostname = 'p:'.$argHostname; if ($this->ssl_key || $this->ssl_cer || $this->ssl_ca || $this->ssl_ccapath || $this->ca_cipher) { mysqli_ssl_set($this->_connectionID, $this->ssl_key, $this->ssl_cer, $this->ssl_ca, $this->ssl_capath, $this->ssl_cipher); }
The text was updated successfully, but these errors were encountered:
MySQL has the ability to have secured connections via a certificate. This is quite simple in Azure to configure. However ADODB's connect function inits-and-connects in one fell swoop, and the SSL trigger needs to happen between the two if it's not part of the my.cnf. I'd like to propose an extension to the adodb-mysqli.inc.php code:
class ADODB_mysqli extends ADOConnection { ... var $multiQuery = false; var $ssl_key = false; var $ssl_cer = false; var $ssl_ca = false; var $ssl_capath = false; var $ssl_cipher = false;
...
if ($persist && PHP_VERSION > 5.2 && strncmp($argHostname,'p:',2) != 0) $argHostname = 'p:'.$argHostname; if ($this->ssl_key || $this->ssl_cer || $this->ssl_ca || $this->ssl_ccapath || $this->ca_cipher) { mysqli_ssl_set($this->_connectionID, $this->ssl_key, $this->ssl_cer, $this->ssl_ca, $this->ssl_capath, $this->ssl_cipher); }
The text was updated successfully, but these errors were encountered: