fix: update cryptographic hash and encryption
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test -
Documentation
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Anthos -
Azure -
GCP -
IBM
Does this follow conventional commits spec?
-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
- SHA-1 is no longer considered as secure. Upgrade to SHA-512.
- TLS1.3 has already removed support of AES CBC. Upgrade to AES GCM as it is designed to provide both integrity and confidentiality