You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: