William Woodruff

Sorry, this fell of my radar completely. Trying now...

I can't reproduce this locally: ``` $ ./winchecksec ../test/assets/32/*.exe ``` ...audits all of the EXEs under that directory. Example output: ```console Results for: ../test/assets/32/pegoat-authenticode.exe Dynamic Base : "Present" ASLR :...

Looking at your globs: I'm not sure if you were running in a directory that had any executables or other auditable files in it. The ZSH error is the one...

Ping: were you able to resolve this? I can confirm that globs work correctly for me locally, on all of Winchecksec's supported hosts.

...except for Windows of course, since Windows doesn't have shell-native globbing. Looks like I misread this a little: if you're still seeing the problem on Windows, it's because the Windows...

> Can you provide an example binary that would trigger these IMAGE_LOAD_CONFIG_DIRECTORY warning messages? What if any checks do you want to execute if this exception is encountered? I don't...

Looks like getting this information will be a little annoying: it's stored in the "extended DLL characteristics", which are an entry of type `IMAGE_DEBUG_TYPE_EX_DLLCHARACTERISTICS=20` in the debug data directory entry...

I'm going to push this to 2.1, since the right way to do it is with some pe-parse changes.

Thanks for the report. Is there a flag or field we can test that confirms that a particular DLL only contains resources? If there is, then I agree that we...

Also, could you clarify what you mean by "resource DLL"? I assumed that it meant a DLL containing only static program resources (like icons, fonts, etc.) but it looks like...