Apple code signing Mach-O data structures

I wanted to share that I have just published a crate that implements support for Apple's code signatures: https://crates.io/crates/tugger-apple-codesign.

I'm mentioning this in the goblin issue tracker because a) I used goblin extensively (thank you so much for goblin!) b) there are a lot of data structures related to code signing embedded in the Mach-O and goblin may want to consider parsing them.

If goblin were interested in parsing these data structures, you have choices of how deep into the data structures you want to go. If you are interested in learning more, most of the Mach-O primitives are defined in https://github.com/indygreg/PyOxidizer/blob/main/tugger-apple-codesign/src/macho.rs. https://github.com/indygreg/PyOxidizer/blob/main/tugger-apple-codesign/src/specification.rs has some more documentation.

I'm not volunteering to add the support to goblin: just informing you for your consideration. I'm also here to consult if you want to pick my brain.

Start by reading tugger-apple-codesign/src/macho.rs and tugger-apple-codesign/src/specification.rs to understand the referenced Mach-O code-signing structures, then inspect goblin’s existing Mach-O parsing scope. Done means agreeing on whether goblin should support these structures and defining a concrete implementation scope.