[TOOL] ipsw #2662
Closed
[TOOL] ipsw #2662
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cpholguera
requested changes
Jul 12, 2024
|
|
||
| IPSW calls itself an "iOS/macOS Research Swiss Army Knife". In general, IPSW allows you to obtain iOS specific files (IPSW, OTA, ...) and also statically analyze them. For application analysis, the most interesting features are the Objective-C and Swift class-dumps. Other features are available (kernelcache parser, device-tree parser, disassembler, etc) but are only useful if you're analyzing the security of the OS itself. | ||
|
|
||
| ## Extracting Objective-C Class Information |
There was a problem hiding this comment.
These kinds of things belong in the corresponding MASTG-TECH as a subsection. This way once we enable xrefs for these components we'll be able to navigate to these examples of use right from the tool.
|
added in #2849 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was looking through the style guide for code blocks, and I'm not entirely sure how we should document the generic tool commands. The guide says to use placeholders for arguments, but then we can't show any useful output. Or we only use placeholders, but the output seems useful in this case.
I also played around with the fold-out admonition for the full command output, though I didn't add it for swift-dump since it would be 18k lines of code.
Finally, I added a 'host' meta tag. Could be useful info, no?