Difference between revisions of "Shattered SHA-1 Function"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
It is public knowledge that Google had cracked [[SHA-1]] and presented a website called:[https://shattered.io shattered.io] to disclose their findings. You can even test if your document encoded using SHA-1 has [[name collision]]s or not. | It is public knowledge that Google had cracked [[SHA-1]] and presented a website called:[https://shattered.io shattered.io] to disclose their findings. You can even test if your document encoded using SHA-1 has [[name collision]]s or not. | ||
Name collision is a situation where names chosen by Secure Hash Algorithms ([[SHA]]) to represent a specific data object maybe shared by two different data objects. This name collision problem could allow one to submit a '''fake''' document or '''fake''' data object that has the same digital digest (the name), therefore confound the authenticity of information. An example of name collision can be found on [https://shattered.io shattered.io]. | Name collision is a situation where names chosen by Secure Hash Algorithms ([[SHA]]) to represent a specific data object maybe shared by two different data objects. This name collision problem could allow one to submit a '''fake''' document or '''fake''' data object that has the same digital digest (the name), therefore confound the authenticity of information. An example of name collision can be found on [https://shattered.io shattered.io]<ref>{{:Paper/The first collision for full SHA-1}}</ref>. | ||
<noinclude> | <noinclude> | ||
{{PagePostfix | {{PagePostfix | ||
|categories={{#invoke:Utility| | |categories={{#invoke:Utility|returnListOfCategoryFromString|Hash Function, Hash Collision}} | ||
}} | |||
</noinclude> | </noinclude> | ||
Latest revision as of 09:29, 2 July 2022
It is public knowledge that Google had cracked SHA-1 and presented a website called:shattered.io to disclose their findings. You can even test if your document encoded using SHA-1 has name collisions or not. Name collision is a situation where names chosen by Secure Hash Algorithms (SHA) to represent a specific data object maybe shared by two different data objects. This name collision problem could allow one to submit a fake document or fake data object that has the same digital digest (the name), therefore confound the authenticity of information. An example of name collision can be found on shattered.io[1].
References
- ↑ Stevens, Marc; Bursztein, Elie; Karpman, Pierre; Albertini, Ange; Markov, Yarik (2017). The first collision for full SHA-1 (PDF). local page: Shattered.io.