Timeline for Convert identical files to hardlinks
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2017 at 0:50 | comment | added | Gilles 'SO- stop being evil' | @DarkHeart Accidental: two files just happen to have the same hash, by coincidence. For MD5, the probability is negligible if you have less than about ten quintillion files (birthday problem. Deliberate: someone creates a pair of files, on purpose, that are not identical but have the same hash. This was first done for MD5 with massive calculations in 2004, and nowadays it is known how to do it for instantly MD5 and with massive calculations for SHA-1, but no one has a clue how to do it for SHA-256. | |
| May 28, 2017 at 0:36 | comment | added | user14755 | @Gilles - accidental and deliberate? What does this mean? | |
| May 27, 2017 at 23:32 | history | edited | Kusalananda♦ | CC BY-SA 3.0 | added 431 characters in body |
| May 27, 2017 at 23:09 | history | edited | Kusalananda♦ | CC BY-SA 3.0 | deleted 2 characters in body |
| May 27, 2017 at 23:02 | comment | added | Gilles 'SO- stop being evil' | Note that with MD5, there is no risk of accidental collisions, but deliberate collisions are possible. Use SHA-256 instead if deliberate collisions are a concern. | |
| May 27, 2017 at 23:01 | comment | added | Gilles 'SO- stop being evil' | There's an existing wheel for the duplicate finding: fdupes. Pity it has a delete option, but no hardlink option. | |
| May 27, 2017 at 20:23 | history | edited | Kusalananda♦ | CC BY-SA 3.0 | added 169 characters in body |
| May 27, 2017 at 20:19 | history | undeleted | Kusalananda♦ | ||
| May 27, 2017 at 20:18 | history | deleted | Kusalananda♦ | via Vote | |
| May 27, 2017 at 20:17 | history | answered | Kusalananda♦ | CC BY-SA 3.0 |