Chris is correct -- maybe this will help explain...

Most software companies try to incorporate defenses against malware exploits and patch security vulnerabilities, while those writing malware do their best to circumvent those efforts. Code signing can help by trying to make sure the file(s) you download are the originals and have not been altered. Windows warns you when it sees an unsigned program file or driver, hoping that folks will do just as you did, Grandpappy, & say: "Hey, wait a minute." Malware developers have ways to get around that. Files can be altered without effecting their signature, signing certificates can be stolen or forged, they can use vulnerable signed driver files, they can avoid using files entirely, e.g., adding scripts to the registry, and so on. Most developers go to the expense of using code signing if for no other reason than to avoid a bunch of people questioning whether their app contains malware, but as Chris says, those signatures are by no means a guarantee.

learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/deployment/use-code-signing-for-better-control-and-protection

wikipedia.org/wiki/Code_signing

mike  –  8 months ago  –  このコメントは役に立ちましたか？ はい | いいえ (+16)

翻訳