Closed greut closed 5 years ago
I've tried to avoid adding such a possibility in the past, e.g. https://github.com/exoscale/cs/pull/18 and https://github.com/exoscale/cs/pull/27
The reasoning is that an insecure setup should be either hard to get or it should be obvious that it's insecure. If there really is no other way I'd love something in the spirit of hdparm
's --yes-i-know-what-i-am-doing
and --please-destroy-my-drive
flags, i.e. something more glaring than verify=False
.
@brutasse requests comes with its own set of warnings once false is set.
@brutasse verify = false
still does nothing useful, but dangerous_no_tls_verify = true
does.
This allows such configuration, which is mostly useful for special developer cases.
http://docs.python-requests.org/en/master/user/advanced/?#ssl-cert-verification