Defender Application Control or Defender SmartScreen – what can you do to not be blocked by it

Ever wondered why do you get one of these popups for your Windows program, despite of the fact that it is signed with a standard code signing certificate ? Applications that are signed with a standard code signing certificates need to have a positive reputation in order to pass the Smart Screen filter. Microsoft establishes the reputation of an executable based upon the number of installations world wide of the same application. Since you haven’t published your application as yet (and therefore the reputation hasn’t been established as yet), the Smart Screen will continue to flag the application. If you have a standard code signing certificate, some time will be needed for your application to build trust. Microsoft affirms that an Extended Validation (EV) Code Signing Certificate allows to skip this period of trust building. According to Microsoft, extended validation certificates allow the developer to immediately establish reputation with SmartScreen. Otherwise, for some time, until your application builds trust, the users will see a warning like “Windows Defender Smartscreen prevented an unrecognized app from starting. Running this app might put your PC at risk.”, with the two buttons: “Run anyway” and “Don’t run”. In newer Windows version you see the…

Sign files unattended in batch mode while having an eToken (no password popup!) (updated)

Expanding on answers already in this thread, it is possible to provide the token password using the standard signtool program from microsoft. 1. Export your public certificate to a file from the SafeNet Client  2. Find your private key container name   3. Find your reader name  4. Format it all together The eToken CSP has hidden (or at least not widely advertised) functionality to parse the token password out of the container name. The format is one of the following []=name [reader]=name [{{password}}]=name [reader{{password}}]=name Where: reader is the “Reader name” from the SafeNet Client UI password is your token password name is the “Container name” from the SafeNet Client UI Presumably you must specify the reader name if you have more than one reader connected – as I only have one reader I cannot confirm this. 5. Pass the information to signtool /f certfile.cer /csp “eToken Base Cryptographic Provider” /k “<value from step 4>” any other signtool flags you require Example signtool command as follows signtool sign /f mycert.cer /csp “eToken Base Cryptographic Provider” /k “[{{TokenPasswordHere}}]=KeyContainerNameHere” myfile.exeUpdate:This doesn’t work after updating the key.Check this thread for more details: https://stackoverflow.com/questions/17927895/automate-extended-validation-ev-code-signing

%d bloggers like this:

By continuing to use the site, you agree to the use of cookies and to its Privacy Policy more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.