working on the windows program compatibility team must be hell on earth
if you want to understand true hell, become a windows application compatibility programmer
all of these are sourced from here: http://ptgmedia.pearsoncmg.com/images/9780321440303/samplechapter/Chen_bonus_ch01.pdf
For example, one
useful shim is known as HeapPadAllocation; it is applied to programs that
have heap buffer overrun bugs. The shim intercepts calls to the
HeapAllocate function and adds a specified amount to the requested size.
That way, when the program overruns a buffer, it merely corrupts the padding
rather than corrupting the next heap block.
some random guy in the mid seventies: hey how about we do [seemingly good idea with nasty underlying assumptions]
raymond chen, today: and that's why windows reports that it only has 640k of memory if your locale is set to hebrew and the PID of explorer is a prime number during a leap second
this seems like a good time to drop another reminder that a windows registry file is called a hive because someone on the windows team had a fear of bees and the person developing the registry was being a jerk
Make sure you get the right Raymond Chen.
There's more than one at Microsoft.
@lynnesbian that's hilarious tbh
@lynnesbian at this point he could just be making these up and who would ever guess
@lynnesbian the registry hives story seems pretty par for the course from my own experiences TBH.
Also thank you for this thread, it is pure gold (and I needed something to take my mind off more depressing stuff).
@lynnesbian Every part of this thread reminds me of all the fancy Windows exploits that have been retained purely for compatibility.
@firstname.lastname@example.org's anti-chud pro-skub instance for funtimes