I can't take THAT seriously. At least not all of it. The part that interested me most:
> 4. Should I find such vulnerability in many applications as I can? > > You should not. It's just a waste of time and your energy. Focus on most > popular application types/classes. If, say, DWM.dll is exploitable, why not point *that* out rather than point out the many applications that are using it (wrongly)? Oh, and the "report". For obvious reasons, I cannot include the full report. If I missed passing any detail, just ask and I'll fix right away. http://img189.imageshack.us/img189/4801/31998033.png On Thu, Sep 9, 2010 at 8:10 PM, YGN Ethical Hacker Group <[email protected]> wrote: > Hi Christian > > The reason I use "Clean" doesn't mean (or I'm not accusing) your > Windows is infected. > It's better to test DLL Hijacking in Clean Copy of Windows without any > prior applications messup. > > Please take a look at > http://core.yehg.net/lab/pr0js/texts/when_testing_for_dll_hijacking.txt > > We thank ACROS Security for bringing life to this issue. > We'll take social responsibility as a security community to stop this > issue as much as we could. > _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
