http://bugs.winehq.org/show_bug.cgi?id=24654
--- Comment #7 from Juan Lang juan_lang@yahoo.com 2010-10-08 07:18:14 CDT --- (In reply to comment #6)
My guess at this point is that the authenticode policy (#0002) is supposed to ignore time validity even when not explicitly stated. Tests needed for that, of course.
Tests show this surmise is incorrect, and that the change is itself correct. So the question is where that bad date is coming from.