[HN Gopher] An open-source implementation of Apple code signing ...
       ___________________________________________________________________
        
       An open-source implementation of Apple code signing and
       notarization (2022)
        
       Author : tosh
       Score  : 117 points
       Date   : 2024-04-15 15:36 UTC (7 hours ago)
        
 (HTM) web link (gregoryszorc.com)
 (TXT) w3m dump (gregoryszorc.com)
        
       | bengarney wrote:
       | The code signing process has sucked and always been deeply
       | cryptic, even on macOS - getting something usable and improvable
       | that's cross platform is a fantastic win.
        
       | notamy wrote:
       | (2022)
        
         | atonse wrote:
         | Yes please add 2022, because when I looked at the PR, I was
         | wondering why it took nearly 2 years to release after the PR
         | was merged.
        
         | dang wrote:
         | Added. Thanks!
        
       | swolpatrol wrote:
       | this is great. I remember having to write a build system that
       | fulfills Apple's shitty requirements for signing on their
       | service, and it sucked hard.
        
       | riedel wrote:
       | Original discussion:
       | https://news.ycombinator.com/item?id=32386762
        
         | dang wrote:
         | Thanks! Macroexpanded:
         | 
         |  _Achieving an open-source implementation of Apple Code Signing
         | and notarization_ -
         | https://news.ycombinator.com/item?id=32386762 - Aug 2022 (51
         | comments)
        
           | jraph wrote:
           | Off topic but I've seen you mention "Macroexpanded" a lot of
           | times, is it something regular users can do, and how?
        
             | codetrotter wrote:
             | From one I've understood, that's referring to Lisp code
             | that runs as dang and automatically makes this sort of
             | reply where it takes links to stories that people comment,
             | and it replies with title of story, month and year it was
             | posted and number of comments.
             | 
             | Only dang can do that sort of thing. Not us mere mortals.
        
             | carbotaniuman wrote:
             | I think it's literally just dang typing out the title and
             | giving more context.
        
       | masterphi wrote:
       | This tool works great! (I've only used it for signing and
       | notarizing MacOS apps)
       | 
       | For anyone looking for the newest release:
       | https://github.com/indygreg/apple-platform-rs/releases
        
       | xyst wrote:
       | How does signing work here? You submit a certificate to Apple
       | which validates who you or organization. Then with your "signed"
       | app, end users can see its source come from you or organization.
        
       | flohofwoe wrote:
       | Title is a bit confusing in that this doesn't seem to be a open
       | source implementation of the actual notarization process. It's
       | "just" a tool which talks to Apple servers to handle the
       | notarization (if I'm reading this right:
       | https://github.com/marketplace/actions/apple-code-signing). I
       | guess the main advantage over Apple's tool is that it also runs
       | on Linux and Windows.
        
       | craigching wrote:
       | We have an enhancement opened with Apple to have a way to delete
       | .cstemp files if the tool runs into them. You'd think we could
       | just add a `find . -name '*.cstemp' -exec rm {} \;` to our build
       | toolchains before building, but we're in a large mono-repo and
       | that would add a lot of time to our builds. Having something like
       | a `--force` to delete the .cstemp files instead of quitting and
       | reporting an error would make us change to this tool pretty
       | quickly I'd think.
        
       ___________________________________________________________________
       (page generated 2024-04-15 23:00 UTC)