Hacker News Reader

Quackmaticon A Tale of Two File Names: deconstructing the checksum in Windows 8.3 file names

I've tried it. It works (this is on NTFS) and the end result is a little anticlimactic: https://usn.pw/blog/gen/2015/06/09/filenames/#follow-on-coll...

Quackmaticon A Tale of Two File Names: deconstructing the checksum in Windows 8.3 file names

That's worth trying. Inducing a bug in kernel code could be interesting.

Quackmaticon A Tale of Two File Names: deconstructing the checksum in Windows 8.3 file names

If the checksums collide, then the number after the tilde is incremented again, (eg. SOBC84~2.ASP). This time, it won't stop at ~4, so you can go up to ~10 and beyond. The file name will be shortened accordingly to fit the number in (eg. SOBC8~10.ASP). This was tested on Windows 7 x64.

Quackmaticon A Tale of Two File Names: deconstructing the checksum in Windows 8.3 file names

> The first 8 digits of pi are 3.14159265

Those are the first 9 digits if you count 3 - the 9 at the end is the 9th digit, not the 8th, so the first 8 digits are correct. You're correct about the ANSI C part though, it's actually C99 - I've corrected that part. Thanks.