This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
FR: Support for "deep" codesigning. #30
Comments
|
Came here to submit a ticket for this. I have an app made with py2app which bundles a ton of files and the notorization service whined it couldn't accept any non-signed files. Maybe I can make a PR for this. 🤔 |
darkvertex
added a commit
to darkvertex/gon
that referenced
this issue
Apr 6, 2021
|
Here we go: ✨ #42 ✨ |
vHanda
added a commit
to GitJournal/GitJournal
that referenced
this issue
Aug 25, 2021
My experiment with gon. I think this - mitchellh/gon#30 - might fix the problem I'm having, but I'm really exhausted with all of this, so I'll try again another day.
latonz
added a commit
to latonz/gon
that referenced
this issue
Dec 21, 2021
Implements issue mitchellh#30, a way to pass "--deep" flag to "codesign" tool.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using gon is a great experience - however, signing
.apppackages, is not.As it stands now, each individual piece of code (binaries, libraries, frameworks) contained in the
.appmust be manually specified in the "source" config. This leads to wasted iteration cycles of having to manually add each failed item following a failed notarisation when developing on the package.Now - I don't know if specifying each individual item is considered a feature or not - is this a "we need to be concise", or an oversight?
If the first - would be great to be able to fail-fast at codesign, instead of failing at notarisation (which can take a while)
If the second - support for signing entire
.appfiles in one shot would be great. Whether that be by adding support forcodesign's--deepflag (not sure if that satisfies this usecase), or some logic which is able to find and sign the prerequisites in the correct order.Thanks for the tool though, it's a great help :)
The text was updated successfully, but these errors were encountered: