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
With recent update of the OpenSSL, some of the ciphers have been marked as deprecated/insecure. So, when "node-mysql" is used on nodejs versions before 0.12, the default cipher used is not secure enough and the connection is not established.
Allow specification of "cipher" as option in the SSL options when instantiating the SSL connection (ie for the end user while creating the pool). We already allow specification of "ca", "key" and "cert".
Another solution: "ssl" option in createPool function should take the object and pass this object (preferably AS-IS) to the TLS and use it to establish the connection.
Hi @jp9 , accepting the ciphers option sounds fine to me. I just committed the new feature to master, if you can try it out and confirm that it works for the given use case :)
With recent update of the OpenSSL, some of the ciphers have been marked as deprecated/insecure. So, when "node-mysql" is used on nodejs versions before 0.12, the default cipher used is not secure enough and the connection is not established.
See more details here:
http://stackoverflow.com/questions/31277667/dh-key-too-small-google-cloudsql-ssl
Proposed solution:
So it will end up looking like this:
The text was updated successfully, but these errors were encountered: