Re: PE module: 'not' logic conditions will match on non-PE files - should pe functions first check if file is PE ?

This is likely due to the change made recently where comparing with UNDEFINED values now evaluates to false. It used to evaluate to UNDEFINED. > But shouldn't pe module conditions check first if the file is a PE header or > valid base PE, then fail if the file isn't ? Functions in the pe module

Re: PE module: 'not' logic conditions will match on non-PE files - should pe functions first check if file is PE ?

That makes sense, thanks Wesley I agree the condition should check is_pe The case where I encountered this from, we had an unwrapped *or* condition following a *uint16(0) == 0x5a4d and* , which caused that condition by itself to match on any non-PE so wrapping the or'ed condition statements in par