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 "/usr/lib/python2.7/httplib.py", line 844, in send
self.connect()
File "/usr/lib/python2.7/dist-packages/boto/https_connection.py", line
126, in connect
context.load_cert_chain(certfile=self.cert_file, keyfile=self.key_file)
TypeError: coercing to Unicode: need string or buffer, NoneType found
This is because I do not use client certificates.
After that I got duplicity working again and it connects just fine now.
sob., 29 wrz 2018 o 21:54 Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
napisał(a):
> 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 like missing SNI support.
> Could you please try if the patch attached works? It is completly
> untested it just looks like it might work…
>
> Sebastian
>
--
Witold Baryluk
My PGP keys for 2017-02-17 - 2019-02-17:
5B8C 48CB 8B2F CF53 CA55 0995 16D9 6FA2 20A8 F130
https://functor.xyz/pgp/witold.baryluk-gmail.gpg.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=0x16D96FA220A8F130
