Discussion in 'ESET NOD32 Antivirus' started by vtol, May 30, 2010.
counting down, Eset care to get it fixed? Quality assurance and Compliance department on vacation?
New installers will be signed using a new certificate.
Many thanks Marcos.
Can you clarify something please? I've got 5 or 6 PCs to roll out next week, am I likely to have problems pushing out 4.2.40 due to this? Or will clients see warning dialogs?
Sorry if it's a lame question, I've not dealt with code-signing cert expiry before.
you might get them on WIN 7 64bit where drivers have to have a valid code signature. the eset driver eamonm.sys is using the very same certificate. hence there might be alert windows popping up after June 09.
Not to worry. You won't be getting any errors nor issues as a result of ESET's code signing certificate expiring- ESET has prudently chosen to use a timestamping service which ensures that even if their certificate expires, the signature will still verify correctly.
If you are still worried about this, try setting your computer clock to sometime beyond the expiry date of the certificate, e.g. 6 July 2010. You will see that the certificate still verifies and nothing abnormal happens (except that your computer clock is off by a month!)
Microsoft certificate which has expired in 2007, installer is still valid
ESET's timestamped installer
that a driver install on win 7 64bit?
the certificate is also installed in the IE as root certificate and being used when having SSL protocol filtering enabled. would not be surprised if that caused havoc after June 09 when having SSL traffic injected as browsers will recognise it as expired then.
A root certificate is generated as soon as SSL checking gets enabled. If you disable SSL checking and re-enable it, the root certificate will be generated from scratch.
Separate names with a comma.