WIP: Code signing data parsing

[woodruffw]

In progress.

Closes #262.

[BrewTestBot]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[BrewTestBot]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[BrewTestBot]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[BrewTestBot]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[BrewTestBot]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[rickmark]

So I think we should move from LinkeditDataCommand to the idea of a meta-programming model where the various LC_ commands are mapped too a class (LC_CODE_SIGNING => CSSuperBlob). Today the fact that it groups unrelated things feels off.

[woodruffw]

Could you clarify what unrelated things are currently being grouped? The current mapping is from each load command’s ID to the parsed form, with a generic `LoadCommand` as fallback for when we don’t know how to parse an ID. Sent from mobile. Please excuse my brevity.

…

On Jan 18, 2022, at 7:41 PM, Rick Mark ***@***.***> wrote:  So I think we should move from LinkeditDataCommand to the idea of a meta-programming model where the various LC_ commands are mapped too a class (LC_CODE_SIGNING => CSSuperBlob). Today the fact that it groups unrelated things feels off. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were assigned.