My testing appears to confirm that juju-deployer is broken by this which I don't think we can do.
I also couldn't confirm the fix with the command ./testssl.sh localhost:37017 - but juju-deployer broke with a ssl error. Should I be looking somewhere else, or is there some sort of problem doing this from localhost?
Because I can't test with testssl.sh I'm not sure how easy this would to workaround as I'm not 100% sure what it's actually offering TLS wise.
My testing appears to confirm that juju-deployer is broken by this which I don't think we can do.
I also couldn't confirm the fix with the command ./testssl.sh localhost:37017 - but juju-deployer broke with a ssl error. Should I be looking somewhere else, or is there some sort of problem doing this from localhost?
Because I can't test with testssl.sh I'm not sure how easy this would to workaround as I'm not 100% sure what it's actually offering TLS wise.
Fixes for python in trusty are being tracked: /bugs.launchpad .net/ubuntu/ +source/ python2. 7/+bug/ 1348955 /bugs.launchpad .net/ubuntu/ +source/ python2. 7/+bug/ 1443704
https:/
https:/