On 2012.04.29 06:42, Arnon Gilboa wrote: >> I see that you used wdi_register_logger() in an "Hack for wdi logging" >> section (currenlty disabled). >> Can you elaborate on the limitation you found there and if you would >> like an enhancement of libwdi's logging facility? >> > I simply wanted wdi used by the service to log to a file instead of a > pipe/stdout, so I gave it dummy args and patched about 5 lines in the > libwdi logger code. Do you think my patch for that will be useful by others?
Not sure. My current view is that standard Windows applications (even ones that don't actually have a visible Window, such as a service) that want to get some logging and can't use stdout would use the standard Windows messaging functionality, even if that means creating a hidden Windows where the messages can be directed to. This is what wdi_register_logger() provides, and because the creation of windows is the core of Windows, the overhead is expected to be minimal. I guess I'll have to see if other people see the current logging options of libwdi as limited. >> Also, since you are installing an Microsoft's WinUSB driver only, and >> not altering the inf, there should be little security concerns with >> regards to the driver installation itself. >> > Not altering the inf? libwdi is patching it. I meant, you're not altering the inf compared to how it would created from an official libwdi app, such as Zadig. Regards, /Pete ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusbx-devel
