Bug#909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google Cloud Storage) backend.

2018-10-04 Thread Sebastian Andrzej Siewior
control: forwarded -1 https://github.com/boto/boto/pull/3836 On 2018-09-30 22:17:05 [+0200], Witold Baryluk wrote: > Needed a small change to your patch: > > Line 126 in boto/https_connection.py in connect function needs to be > protected by check:: > > 126 if self.key_file: >

Bug#909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google Cloud Storage) backend.

2018-09-30 Thread Witold Baryluk
Needed a small change to your patch: Line 126 in boto/https_connection.py in connect function needs to be protected by check:: 126 if self.key_file: 127 context.load_cert_chain(certfile=self.cert_file, keyfile=self.key_file) otherwise I got: File

Bug#909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google Cloud Storage) backend.

2018-09-29 Thread Sebastian Andrzej Siewior
control: tags -1 patch On 2018-09-25 03:04:49 [+0200], Witold Baryluk wrote: > Now it takes few minutes on any command, and then errors out: > Cleaning older backups > Traceback (innermost last): … > SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed > (_ssl.c:726) It looks

Bug#909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google Cloud Storage) backend.

2018-09-24 Thread Witold Baryluk
Package: python-boto Version: 2.44.0-1 Severity: normal Not sure if boto, or duplicity issue. duplicity with GS was working fine for year or two, and started failing few weeks ago. Now it takes few minutes on any command, and then errors out: Cleaning older backups Traceback (innermost