Issue:
Does PME 8.x use SHA-1 secure hash algorithm?
Product Line:
Power Monitoring Expert (PME)
Environment:
Secure Hash Algorithm and Power monitoring Expert
Cause:
Need to know if PME 8.x uses SHA-1 secure hash algorithm
Resolution:
PME 8.0 and PME8.1 does not use SHA-1 or SHA-2 for anything security-related.
PME 8.2 does not use SHA-1 for any security related function.
PME 8.2 uses SHA-2 (specifically a 512 bit hash) as a part of password protection.
In cryptography, SHA-1 (Secure Hash Algorithm 1) is a cryptographic hash function designed by the United States National Security Agency and is a U.S.
Federal Information Processing Standard published by the United States NIST.[3]
SHA-1 produces a 160-bit (20-byte) hash value known as a message digest.
A SHA-1 hash value is typically rendered as a hexadecimal number, 40 digits long.
SHA-1 is no longer considered secure against well-funded opponents.
In 2005, cryptanalysts found attacks on SHA-1 suggesting that the algorithm might not be secure enough
for ongoing use,[4] and since 2010 many organizations have recommended its replacement by SHA-2 or SHA-3.
Microsoft, Google, Apple, and Mozilla have all announced that their respective browsers will stop accepting
SHA-1 SSL certificates by 2017.
Does PME 8.x use SHA-1 secure hash algorithm?
Product Line:
Power Monitoring Expert (PME)
Environment:
Secure Hash Algorithm and Power monitoring Expert
Cause:
Need to know if PME 8.x uses SHA-1 secure hash algorithm
Resolution:
PME 8.0 and PME8.1 does not use SHA-1 or SHA-2 for anything security-related.
PME 8.2 does not use SHA-1 for any security related function.
PME 8.2 uses SHA-2 (specifically a 512 bit hash) as a part of password protection.
In cryptography, SHA-1 (Secure Hash Algorithm 1) is a cryptographic hash function designed by the United States National Security Agency and is a U.S.
Federal Information Processing Standard published by the United States NIST.[3]
SHA-1 produces a 160-bit (20-byte) hash value known as a message digest.
A SHA-1 hash value is typically rendered as a hexadecimal number, 40 digits long.
SHA-1 is no longer considered secure against well-funded opponents.
In 2005, cryptanalysts found attacks on SHA-1 suggesting that the algorithm might not be secure enough
for ongoing use,[4] and since 2010 many organizations have recommended its replacement by SHA-2 or SHA-3.
Microsoft, Google, Apple, and Mozilla have all announced that their respective browsers will stop accepting
SHA-1 SSL certificates by 2017.