Now its final SHA-1 is no more secured and path to deprecation!!
Look at the google announcement:
https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
It has been finally proven that the SHA-1 usage in certificates are vulnerable and need to be deprecated.
If you have any certificates you can find what algorithm it uses:
test-vm:~>/usr/bin/openssl x509 -in MyCACert.pem -noout -text | grep "Signature Algorithm"
Signature Algorithm: sha256WithRSAEncryption
Signature Algorithm: sha256WithRSAEncryption
You can also connect to the webserver and see that on the browser security overview.
Look at the google announcement:
https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
It has been finally proven that the SHA-1 usage in certificates are vulnerable and need to be deprecated.
If you have any certificates you can find what algorithm it uses:
test-vm:~>/usr/bin/openssl x509 -in MyCACert.pem -noout -text | grep "Signature Algorithm"
Signature Algorithm: sha256WithRSAEncryption
Signature Algorithm: sha256WithRSAEncryption
You can also connect to the webserver and see that on the browser security overview.
Just a brief:
What is SHA-2?
SHA-2 (Secure Hash Algorithm 2). The algorithms are collectively known as SHA-2, named after their digest lengths (in bits): SHA-256, SHA-384, and SHA-512Use Cases?
The SHA-2 hash function is implemented in widely used security applications and protocols, including TLS and SSL, PGP, SSH, S/MIME, and IPsecTimeline:
SHA-1 should be deprecated by January 2017. (Posting this blog after the period. Idiot ...)
