On 26.01.2017 04:47, az wrote:
> according to the boto release notes for 2.6.0
> (http://docs.pythonboto.org/en/latest/releasenotes/v2.6.0.html), boto
> now defaults to certificate verification ON instead of opt-in.
>
> i think that's pretty much it, given that boto is now at version 2.45 or
> so.
stable is now boto3, any reason why we still stick with the boto2 ?
> if that is considered not certain enough, then i think all that's necessary would be to
> adjust duplicity/backends/_boto_single.py where storage_uri.connect() is called and change those
> calls so that the validate_certs option is explicitely given.
>
nack.. that would break backward compatibility. we could do that for 0.8.x though..
On 26.01.2017 04:47, az wrote: docs.pythonboto .org/en/ latest/ releasenotes/ v2.6.0. html), boto
> according to the boto release notes for 2.6.0
> (http://
> now defaults to certificate verification ON instead of opt-in.
>
> i think that's pretty much it, given that boto is now at version 2.45 or
> so.
stable is now boto3, any reason why we still stick with the boto2 ?
> if that is considered not certain enough, then i think all that's necessary would be to backends/ _boto_single. py where storage_ uri.connect( ) is called and change those
> adjust duplicity/
> calls so that the validate_certs option is explicitely given.
>
nack.. that would break backward compatibility. we could do that for 0.8.x though..
..ede/duply.net