Jeffrey Altman wrote: > The thawte certificates seem to be acceptable with XP but they > are no longer being accepted by Vista nor are they being accepted > by Microsoft for their Windows Crash Reporting service. The problem > appears to be that only the Verisign Code Signing CA is now a trust > anchor for validating Authenticode signatures.
The Windows Crash Reporting service as well as 64bit kernel mode drivers require a VeriSign certificate, that's documented. But MS claim that there were no difference between common applications signed by a self-made and a commercial Authenticode certificate as long as you trust it explicitly. May be it's just a bug in beta 2 that they will fix. If not, it would be the sentence of death for many freeware and shareware programs. I don't think many people are willing to pay the monopoly fee of $399 anual to VeriSign, just in order to get a more friendly looking, blue security alert. If somebody has created an Authenticode certificate with OpenSSL or makecert that's being accepted by Vista UAP please let me/us know. Thanks, Arno Garrels ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
