118cf2ba8a
We've known this would eventually be necessary for a while [1], and way back in 2017 we started seeing SHA-1 collisions [2]. [1] https://www.schneier.com/blog/archives/2012/10/when_will_we_se.html [2] https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html UpgradeImpact: ============== "sha1" has been removed from the default set of `allowed_digests` in the tempurl middleware config. If your cluster still has clients requiring the use of SHA-1, - explicitly configure `allowed_digests` to include "sha1" and - encourage your clients to move to more-secure algorithms. Depends-On: https://review.opendev.org/c/openstack/tempest/+/832771 Change-Id: I6e6fa76671c860191a2ce921cb6caddc859b1066 Related-Change: Ia9dd1a91cc3c9c946f5f029cdefc9e66bcf01046 Closes-Bug: #1733634 |
||
---|---|---|
.. | ||
account-server.conf-sample | ||
container-reconciler.conf-sample | ||
container-server.conf-sample | ||
container-sync-realms.conf-sample | ||
dispersion.conf-sample | ||
drive-audit.conf-sample | ||
internal-client.conf-sample | ||
keymaster.conf-sample | ||
memcache.conf-sample | ||
mime.types-sample | ||
object-expirer.conf-sample | ||
object-server.conf-sample | ||
proxy-server.conf-sample | ||
rsyncd.conf-sample | ||
swift-rsyslog.conf-sample | ||
swift.conf-sample |