- 21 Nis 2020
- 1,208
- 686
Welcome Turk Hack Team Members,
Problem
I'm trying to use the HASHBYTES() function and I see there is an assortment of hashing algorithms available. What is the difference between each one?
Solution
HASHBYTES(), as the name implies, is a function or algorithm that generates a hash from some input. If you're not familiar with what a hash is, here's a good working definition for a hash function:
hash function - A hash function takes in data and returns back a fixed length block of bits such that any change to the data should result in a different block.
HASHBYTES() is actually a function which provides access to several hashing algorithms. SQL Server 2005 and up have the following protocols (how you specify them in HASHBYTES is in parentheses):
MD 2 (MD2)
MD 4 (MD4)
MD 5 (MD5)
SHA-0 (SHA)
SHA-1 (SHA1)
SQL Server 2012 introduces these additional hashing algorithms:
SHA-2 256 bits AKA SHA-256 (SHA2_256)
SHA-2 512 bits AKA SHA-512 (SHA2_512)
With these options, which should you choose?
If you're looking for something just to quickly differentiate between two blocks of data, then it doesn't make a whole lot of difference.
If, however, you're dealing with hashes for passwords or anything related to security, then your choice can make a big difference.
Hashing Algorithms You Should Probably Avoıd
Since a hash function will return a fixed length block, obviously, there are a finite set of possibilities for the output. Therefore, there's bound to be different inputs that will result in the same output. We call these situations collisions. What is of concern is if a collision can be engineered fairly quickly/cheaply. This is referred to as a collision attack. If a hashing algorithm is susceptible to this type of attack or other attacks with reasonable resources that either (a) allow you to create an identical hash with different input or (b) figure out the input from the hash, then those algorithms should be avoıded. As of the writing of this tip, the following algorithms fall into that list:
MD 2 - developed in 1989 by Ronald Rivest, it generates a 128-bit hash value. It is susceptible to several attacks and is no longer considered cryptopgraphically secure.
MD 4 - Also developed by Rivest (1990), it generates a 128-bit hash value like MD 2. And like MD 2, it is susceptible to a couple of attacks and is no longer considered cryptographically secure.
MD 5 - Developed by Rivest in 1992, it also generates a 128-bit hash value. While we see it used often to "digitally fingerprint" files and docments, it is also considered "broken" and no longer cryptographically secure.
SHA-0 - SHA-0 was withdrawn shortly after being made public due to a "significant" flaw. It generates a 160-bit hash value. It was replaced by SHA-1.
Hashing Algorithms Which Are Good for Now
There is one algorithm in this group, and that's SHA-1 (SHA 1). While it is theoretically possible to generate collisions, in 2012 it's rather expensive to do so, as this Bruce Schneier post points out. In a few years, especially with cloud computing, it should be within the financial resources of organized crime to be able to break the algorithm. As a result, the US government had recommended that government agencies start phasing it out start back in 2010. However, it's still very much in use.
If you're not on SQL Server 2012, SHA-1 is the best choice to use.
Hashing Algorithms Good for the Foreseeable Future
The SHA-2 algorithm comes in several block sizes, of which SQL Server 2012 implements two:
Next Steps
Read up on how to use HASHBYTES() to track and store historical changes in data.
Understand the different between symmetric and asymmetric encryption algorithms.
Learn how to use certificates to encrypt sensitive data in SQL Server.
Read more about the HASHBYTES function
//Quoted. Thanks for reading.
Problem
I'm trying to use the HASHBYTES() function and I see there is an assortment of hashing algorithms available. What is the difference between each one?
Solution
HASHBYTES(), as the name implies, is a function or algorithm that generates a hash from some input. If you're not familiar with what a hash is, here's a good working definition for a hash function:
hash function - A hash function takes in data and returns back a fixed length block of bits such that any change to the data should result in a different block.
HASHBYTES() is actually a function which provides access to several hashing algorithms. SQL Server 2005 and up have the following protocols (how you specify them in HASHBYTES is in parentheses):
MD 2 (MD2)
MD 4 (MD4)
MD 5 (MD5)
SHA-0 (SHA)
SHA-1 (SHA1)
SQL Server 2012 introduces these additional hashing algorithms:
SHA-2 256 bits AKA SHA-256 (SHA2_256)
SHA-2 512 bits AKA SHA-512 (SHA2_512)
With these options, which should you choose?
If you're looking for something just to quickly differentiate between two blocks of data, then it doesn't make a whole lot of difference.
If, however, you're dealing with hashes for passwords or anything related to security, then your choice can make a big difference.
Hashing Algorithms You Should Probably Avoıd
Since a hash function will return a fixed length block, obviously, there are a finite set of possibilities for the output. Therefore, there's bound to be different inputs that will result in the same output. We call these situations collisions. What is of concern is if a collision can be engineered fairly quickly/cheaply. This is referred to as a collision attack. If a hashing algorithm is susceptible to this type of attack or other attacks with reasonable resources that either (a) allow you to create an identical hash with different input or (b) figure out the input from the hash, then those algorithms should be avoıded. As of the writing of this tip, the following algorithms fall into that list:
MD 2 - developed in 1989 by Ronald Rivest, it generates a 128-bit hash value. It is susceptible to several attacks and is no longer considered cryptopgraphically secure.
MD 4 - Also developed by Rivest (1990), it generates a 128-bit hash value like MD 2. And like MD 2, it is susceptible to a couple of attacks and is no longer considered cryptographically secure.
MD 5 - Developed by Rivest in 1992, it also generates a 128-bit hash value. While we see it used often to "digitally fingerprint" files and docments, it is also considered "broken" and no longer cryptographically secure.
SHA-0 - SHA-0 was withdrawn shortly after being made public due to a "significant" flaw. It generates a 160-bit hash value. It was replaced by SHA-1.
Hashing Algorithms Which Are Good for Now
There is one algorithm in this group, and that's SHA-1 (SHA 1). While it is theoretically possible to generate collisions, in 2012 it's rather expensive to do so, as this Bruce Schneier post points out. In a few years, especially with cloud computing, it should be within the financial resources of organized crime to be able to break the algorithm. As a result, the US government had recommended that government agencies start phasing it out start back in 2010. However, it's still very much in use.
If you're not on SQL Server 2012, SHA-1 is the best choice to use.
Hashing Algorithms Good for the Foreseeable Future
The SHA-2 algorithm comes in several block sizes, of which SQL Server 2012 implements two:
- SHA-2 256 bit block size (called SHA-256)
- SHA-2 512 bit block size (called SHA-512)
Next Steps
Read up on how to use HASHBYTES() to track and store historical changes in data.
Understand the different between symmetric and asymmetric encryption algorithms.
Learn how to use certificates to encrypt sensitive data in SQL Server.
Read more about the HASHBYTES function
//Quoted. Thanks for reading.
