Imagine a vendor uses AuthentiCode only to get rid of the yellow UAC warnings. To avoid buying new certificates each year, the vendor could create a Launcher EXE which is signed, requests UAC privileges, and launches the project's EXE file.
Beside the fact that the vendor's program can be cracked without anyone noticing it, I am wondering about following 2 issues:
If someone writes a malicious program, they could use the vendor's launcher to make the victim feel good when they see a blue UAC dialog.
Technically, the vendor didn't sign a malicious code (*), so the vendor isn't "responsible" for the malicious activities, and the CA would probably not revoke the certificate of the vendor.
So, what are the consequences of this Launcher (i.e. is the vendor responsible, and would the CAs revoke his certificate?), and is it true that AuthentiCode can be so easily tricked by using launchers and/or unchecked DLL imports?
(*) the launcher is a rather extreme case; however, nearly every signed executable that runs code from a DLL could be used to execute malicious code (in unsigned/unchecked DLLs). Afaik, the static linking of DLL files do not contain any AuthentiCode check, so that these executables are as evil as the Launcher EXE.