Closed michaelshobbs closed 2 years ago
@otan @mjibson I'm not an SSL expert by any stretch so any pointers here would be great
i'm no expert either, but my guess is those certificates have to be regenerated. maybe worth following https://www.postgresql.org/docs/current/ssl-tcp.html.
this is looking awesome btw!
@otan @mjibson i believe this is good to go now
once this is merged, i'll update #1047 with these commits
this is awesome, cheers buddy
ref: https://github.com/lib/pq/pull/1047#issuecomment-906062580
the
TestSSLClientCertificates
fails on postgres 13 & 12 withssl_test.go:269: remote error: tls: bad certificate
but the other postgres versions seem to work.EDIT: also
TestSSLVerifyFull
fails on golang 1.17 withssl_test.go:104: x509: certificate relies on legacy Common Name field, use SANs instead
. From what I can tell, they removed theGODEBUG=x509ignoreCN=0
flag.