Reminds me of the lock-up bug from the early 00s where specifying DOS era device names would lock up your system. This is still the reason you can't make directories on your Windows system called aux, con, lpt1 etc: https://www.helpndoc.com/documentation/html/Windowsreservedfilenames.html … Old school: https://packetstormsecurity.com/files/10178/SCX-SA-01.txt.html …https://twitter.com/jonasLyk/status/1282538733506568197 …
incredible not all have been found of this kinda bug... but- the old names are still very powerfull, like you can do this:https://twitter.com/jonasLyk/status/1261747345806499841 … or simply delete \GLOBAL??\nul and replace with what you want. now win32 path nul resolves to whatever :)
-
-
It gets sticky pretty fast. Filenames are still an Achilles heel for Windows because of its legacy. The fact that Microsoft Office still can't open two files with the same filename still baffles me.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.