Open stoefln opened 2 months ago
Can you try this for win.sign
config sign.js
const path = require('path')
const { doSign } = require('app-builder-lib/out/codeSign/windowsCodeSign')
/**
* @type {import("electron-builder").CustomWindowsSign} sign
*/
module.exports = async function sign(config, packager) {
// Do not sign if no certificate is provided.
if (!config.cscInfo) {
return
}
const targetPath = config.path
// Do not sign yourFileNamesArray
if (yourFileNamesArray.some(filename => targetPath.endsWith(filename)))) {
return
}
await doSign(config, packager)
}
thanks @mmaietta! Can you tell me which of the files need to be signed? I guess only the myapp.exe, and the installer right?
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
As part of our electron app, we ship a couple of external executables (exe files) that are usually distributed by google (android command line tools). I am not sure, but I think those files are already signed. So during our electron packaging process, we are also signing files, and it seems all executables are signed automatically (by electron-builder), which means that also those android-command-line tools executables are signed again. AFAIS this should be avoided, right? Is there any way to exclude files from signing?
I found this, but it's not answered: https://github.com/electron-userland/electron-builder/issues/3790
Here are the relevant log lines: