![]() In such cases, we recommend that you use the –ssl, –ssl-ca, –ssl-cert, and –ssl-key options so that your MySQL command line client will connect to MySQL in a secure format. ![]() If you do not see a cipher in use, you’re not connected to MySQL securely. ![]() Sometimes production databases have shorter timeouts than dev databases. Please edit your question to tell us what values you have on your two databases. If you want to see for sure that you’re connecting via SSL, you can always log into your MySQL database and enter the ‘\s’ command to see the SSL cipher in use. 1 Please issue this SQL query on both your dev database and the production database. ClearDB supports this option as well, and enables it by invoking the use of default client certificates (or ‘gateway certs’) in our MySQL cluster configurations. Some MySQL clients (for example, certain ‘mysql’ command line tools) know how to connect securely without having to specify any of the –ssl-* options that exist. main monica/docs/installation/update.md Go to file Cannot retrieve contributors at this time 237 lines (173 sloc) 12.6 KB Raw Blame Update your server Generic instructions Updating Heroku instance Importing vCards (CLI only) Importing SQL from the exporter feature Importing SQL into Heroku WARNING: This will delete your current database. Using The MySQL Command Line Client With SSL However, for those who want to connect to ClearDB using SSL encryption, we now have a guide in place that shows you how to do it, as well as provides you with our CA certificate so that you can fully utilize MySQL’s encryption mechanisms. While ClearDB does certainly support this option, we cannot enforce it with all of our customers – some customers simply don’t want to use encryption due to the additional complications that it adds to their configuration. Recently, we’ve been receiving a few requests to connect to ClearDB using client level encryption, or SSL in MySQL. ![]()
0 Comments
Leave a Reply. |