local error: no renegotiation about postgres-to-redshift HOT 2 CLOSED

Hi Samuel,

Yes - that ticket is very relevant! We've hit the same problems at Clever, and have worked around the crypto library's limitations by setting the ssl_renegotiation_limit to be infinite on the databases we use this with. See this Stack Overflow post for details.

From a security standpoint, I would suggest that a very large or infinite renegotiation limit is more secure even than an implementation of renegotiation in the crypto library. It seems incredibly unlikely that any single database query would be large enough for cryptanalysis to take place successfully, and any renegotiation implementation would be complicated and risky. While we have additional security because we only run this within our private network, you should evaluate for yourself how high you want to set the ssl_renegotiation_limit, especially if your traffic traverses the internet.

Please let me know if you have any further questions,
-Colin

from postgres-to-redshift.

Thanks for the quick response. I'll give it a try.

from postgres-to-redshift.