-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate code-signing as part of our release process #1580
Comments
From @phargogh : We now have a host machine at a Stanford data center with our YubiKey installed. Option 1: Install a GHA runner on a VM on this data center machine. This is discouraged by GitHub, due to the potential for running untrusted code on hardware on a trusted network. Option 2, the preferred option.: Ping a cloud function with list of binaries on GCS that need to be signed, adding them to a queue. The VM would pull from the queue to download, sign, & upload. |
Signature files are now pushed to the bucket alongside the .exe file, and we check whether the file exists before enqueueing the exe. RE:natcap#1580
In #1523 we were able to set up a yubikey to sign our binaries. The process for signing binaries was pretty manual: download binary, sign binary, upload binary. It would be fantastic to be able to do this in the cloud as a part of our usual build automation.
The text was updated successfully, but these errors were encountered: