96 |
|
|
97 |
Identifier uniqueness considerations: |
Identifier uniqueness considerations: |
98 |
|
|
99 |
As SHA-1 is regarded as a strongly collision-free |
SHA-1 is regarded as a strongly collision-free |
100 |
cryptographic hash function, as long as no successful |
cryptographic hash function: as long as no successful |
101 |
attacks are found it can be assumed that no two different |
attacks are found it is extremely unlikely that two different |
102 |
byte sequences will ever be generated that have the same |
byte sequences will ever be generated that have the same |
103 |
SHA-1 hash. Therefore, it is reasonable to assume |
SHA-1 hash. Therefore, it is reasonable to assume |
104 |
that no two different Storm blocks will ever be assigned |
that no two different Storm blocks will ever be assigned |