HTTPError: Signing request failed: 400 Bad Request

Using electron-builder, I got HTTPError .

Here is the afterPack script I am using:

const util = require('util')
const childProcess = require('child_process')
const exec = util.promisify(childProcess.exec)

async function evsProcess(appPath) {
  const res = await exec('python3 -m castlabs_evs.vmp sign-pkg --persistent ' + appPath)
  console.log(res.stdout)
}
await evsProcess(context.appOutDir).catch(e => console.log(e))

stdout is:

'Signing: /Users/XXXXX/path/to/project/dist_electron/win-ia32-unpacked/XXXXX.exe\n' +
    ' - Verifying existing VMP signature\n' +
    ' - Signature invalid: Certificate is valid for development only\n' +
    ' - Requesting VMP signature\n' +
    'HTTPError: Signing request failed: 400 Bad Request\n' +
    ' <- InvalidDataError: Failed to generate verification digest\n' +
    " <- NameError: name 'HASH_BLOCK' is not defined\n",

Curiously, building for macOS doesn’t cause any problems, and building for Windows gives this error.

[PhantomNimbi]

Ok, good news that you may have found the problem.

If it persists I need to know the specific version of Electron for Content Security, a.k.a. ECS, that is used - this is different from EVS (which is the VMP signing service/client). There is certainly a possibility that a specific version of ECS has been incorrectly published, but this would mean other versions would still work. I checked the service itself after your last question and there was no problem signing the latest stable ECS release.

I’m not familiar with nativefier but it is also possible, albeit unlikely, that the packager is doing something to the executable that is incompatible with EVS, so a version update there could potentially also be interesting to look at.

I found my issue. My script wasn’t separating the lists properly. The list I had set to use Castlabs_EVS was in fact NOT using Castlabs_EVS due to this error. I managed to get it fixed and am updating my repo with the fixes right now.

[khwaaj]

Since this appears to be solved I’m closing it, feel free to reopen if some issue persists.