Skip to content

New ipsw verify command? #482

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

Closed
2 tasks done
justtryingthingsout opened this issue Jun 2, 2024 · 3 comments
Closed
2 tasks done

New ipsw verify command? #482

justtryingthingsout opened this issue Jun 2, 2024 · 3 comments
Assignees
Labels

Comments

@justtryingthingsout
Copy link

Is your feature request related to a problem? Please describe.

There is currently no way that I know of that allows for the verification of the disks inside of a IPSW using the root hashes, mtrees, and integrity catalogs, apart from a verification by a tool such as img4tool, which might be something worth implementing

Describe the solution you'd like

A ipsw verify command that allows for the verification of the dmgs inside of the ipsws, using the mtree, root hash, and integrity catalogs, as is done by Apple themselves. Could also include other ways of verification, such as the one implemented in img4tool.

Describe alternatives you've considered

Having no command for this, which is fine as well, as this might be a gimmick if img4tool suffices.

Search

  • I did search for other open and closed issues before opening this

Code of Conduct

  • I agree to follow this project's Code of Conduct

Additional context

No response

@blacktop
Copy link
Owner

blacktop commented Jun 2, 2024

I have also been thinking about verification cmds

Add calculated as well as reported hashes in the code signature for MachOs and the DSC (only w/ a flag or -V as it'll be SLOW for DSC etc)

Add a ipsw macho sign --verify cmd OR a ipsw verify macho subcmd if it makes more sense to have a verify category w/ subcmds

Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants