You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a file available for signing is a bit problematic in a public build pipeline. OSX allows a base64 certificate string to be used which can be stored as a secret very simply. Is this an option or a possibility for this package?
The text was updated successfully, but these errors were encountered:
certificate is passed directly to Windows SDK signtool.exe verbatim, whatever it supports, Squirrel supports. Having a ~7000+ byte environment variable might blow the max length for the environment block for a process as well (though I definitely sympathize with the want to not have to inject secret files in CI then mop them up afterwards)
Having a file available for signing is a bit problematic in a public build pipeline. OSX allows a base64 certificate string to be used which can be stored as a secret very simply. Is this an option or a possibility for this package?
The text was updated successfully, but these errors were encountered: