Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Encrypted connection #71

Open
aszenz opened this issue Jun 26, 2024 · 3 comments
Open

Support Encrypted connection #71

aszenz opened this issue Jun 26, 2024 · 3 comments

Comments

@aszenz
Copy link

aszenz commented Jun 26, 2024

I'm trying to connect to a MySQL database that only allows encrypted connections, but there doesn't seem to be a way to do that in DuckDB.
I have a custom CA certificate file that I can normally use in the MySQL client (the ssl_ca parameter). DuckDB has no such parameter so a connection can't be established. Unless I'm overlooking something, it seems DuckDB doesn't support encrypted connections to MySQL. Any help would be greatly appreciated!

Moved from duckdb/duckdb#12676 (comment)

Mytherin added a commit to Mytherin/duckdb_mysql that referenced this issue Sep 5, 2024
Mytherin added a commit that referenced this issue Sep 5, 2024
Implement #71: add SSL connection parameters
@Mytherin
Copy link
Contributor

Mytherin commented Sep 5, 2024

Thanks for the report! I've implemented these options in #85 - I don't have an encrypted MySQL instance myself to test so if you could try it out that would be very helpful.

@aszenz
Copy link
Author

aszenz commented Sep 5, 2024

Thanks for the report! I've implemented these options in #85 - I don't have an encrypted MySQL instance myself to test so if you could try it out that would be very helpful.

Sure, do i need to wait for a release or I can load the master branch version of the extension somehow?

@mattsams89
Copy link

It's obviously not an encrypted connection, but I can confirm the updated version available through the 1.1.0 CLI allows me to set ssl_mode=disabled and successfully connect to an internal DB at work. I was previously getting an SSL error, so this is a game changer!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants