This seems to be something that Mcafee missed out on releasenig new verions of MA. This is problem even with the latest MA 4.8.2.
A customer asked this question last month. Our engineer gave this response:
"All that should mean is that we can’t use that certificate to sign files after 12/31/2013. It should do nothing for existing files that have been signed prior to that time. Internally we will start signing code using a certificate that expires in 2014 instead.
There are types of certificatesthat really do expire on the expiration date (this is intended for SSL – not code signing), but we don’t use those sorts nor does Microsoft (reference on asigning mistake Microsoft made along those lines: http://blogs.technet.com/b/srd/archive/2012/10/09/security-advisory-2749655-and- timestamping.aspx)."
Thank you for clarification.
Men are always learning.