Andrew G

Thanks for the tip, this describes the code signing process which works up and until secure boot (UEFI) is enabled in windows10 - this is the problem I am trying to fix. From this point the drivers have to be countersigned by microsoft by uploading them to theMicrosoft Dev Portal, however I'm running into problems getting this to work. (See also https://www.osr.com/blog/2016/06/02/driver-signing-details-emerge/)

Hi All, We are building our own version of Veracrypt with a minor tweak to suit our embedded systems. I'm now trying to get this signed by microsoft via their dev portal so it will work with Windows 10 (It works fine on earlier Windows versions). Unfortuately the dev portal only appears to accept .cab files as the input (attestation signing). I've approached this by extracting the files from the .exe installer and generating a .cab file, signing it and submitting it, with the expectation that I would...

Hi, After (finally) getting an EV certificate & registering with Microsoft I'm trying to get the files signed by Microsoft. However I'm beginning to think my approach is wrong. Microsoft do not allow the upload of the complete installer .exe to their site for signing, but they do allow upload of .CAB files. I extracted the files from the .exe, created a .CAB file, signed it & uploaded it to their site. I'm expecting to be able to get back a signed version which I can then add extrac32 to in order...

Thanks for your very helpful reply

Hi All, We are building our own version of Veracrypt with a minor tweak to suit our embedded systems. We sign our code with a standard (not EV) code signing certificate. All was well until people tried to install our version on systems with UEFI secure boot enabled: users got the messages "Windows cannot verify the digital signature for this file..." and "A digitally signed driver is required...." [cid:image001.png@01D30144.DAA7CBB0] I have not had to sign software before so this is new to me. I...