3 ms·
This reminded me about an interview to an adware author, in which he told a story about creating unwritable registry keys and file names 'by exploiting an “impe
by ttflee 13y ago
This reminded me about an interview to an adware author, in which he told a story about creating unwritable registry keys and file names 'by exploiting an “impedance mismatch” between the Win32 API and the NT API':
http://philosecurity.org/2009/01/12/interview-with-an-adware-author http://philosecurity.org/2009/01/12/interview-with-an-adware...
The adware registered a key in the Windows Registry with Null unicode in the middle of the string so that the UI of Windows failed to display or modify that string.
- erichocean 13y agoIn my experience, NULL is the least-supported UTF-8 character. Whenever software claims conformance, that's the first thing I check. Personally, I'd have preferred they disallowed it in the standard, but it's too late for that now. Anyone know why it was included (other than the obvious reason that it obeys the encoding rules)?