Open ayufan opened 9 years ago
(2)
We (PreEmptive Solutions) forked iOS Class Guard, creating a new product, called PreEmptive Protection for iOS - Rename (or PPiOS-Rename), that includes the 2nd design. The top level commands implemented are as follows:
ppios-rename --analyze [options] <Mach-O file>
ppios-rename --obfuscate-sources [options]
ppios-rename --translate-crashdump [options] <input file> <output file>
ppios-rename --translate-dsym [options] <input dSYM> <output dSYM>
ppios-rename --list-arches <Mach-O file>
ppios-rename --version
ppios-rename --help
Last week we had an internal discussion about new features and whether they should be in separate commands or should be implemented in current
ios-class-guard
binary. Here are proposals:Which one do you prefer? I personally would opt for option 2, because of commonness of such approach, ie.: vagrant, github client, docker, etc.