Skip to content

How is tls=true useful? #527

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

Closed
aaronkavlie-wf opened this issue Dec 8, 2016 · 2 comments
Closed

How is tls=true useful? #527

aaronkavlie-wf opened this issue Dec 8, 2016 · 2 comments

Comments

@aaronkavlie-wf
Copy link

Issue description

The tls param can be enabled with a custom value, or just true.
It doesn't seem that it's possible to modify the config if set to true, and I'm having trouble figuring out how that is useful. It doesn't appear possible to use a blank config.

Error log

The tls package produced this error on attempt to connect to Amazon Aurora with tls=true:

either ServerName or InsecureSkipVerify must be specified in the tls.Config

Configuration

Driver version (or git SHA):

Go version: go1.7.4 darwin/amd64

Server version: Amazon Aurora

@dveeden
Copy link
Contributor

dveeden commented Apr 3, 2017

#564 also deals with this issue

@julienschmidt
Copy link
Member

Fixed by #564

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