Open ngkogkos opened 6 years ago
+1 on this
In general, it would be great to be able to grep when running any command, e.g.
env | grep BundlePath
or
ios plist cat Info.plist | grep CFBundleExecutable
I know about !
but it seems to work only at the beginning of the line.
While this is not the ideal solution, in the interim you may run once off commands with objection run
. Something like objection run "env" | grep -i BundlePath
should get you your output into a shell you can work with.
Sure, that's usually my workaround ^^ I just wanted to suggest that as an idea for a future feature maybe. It could work similar to radare2's pipes | or internal grep ~. That could be very handy.
Thanks for the answer Leon!
While this is not the ideal solution, in the interim you may run once off commands with
objection run
. Something likeobjection run "env" | grep -i BundlePath
should get you your output into a shell you can work with.
Unfortunately, that won't work for example to grep the output of the list of classes: android hooking list classes
.. which would be nice...
While this is not the ideal solution, in the interim you may run once off commands with
objection run
. Something likeobjection run "env" | grep -i BundlePath
should get you your output into a shell you can work with.Unfortunately, that won't work for example to grep the output of the list of classes:
android hooking list classes
.. which would be nice...
Now I use
objection -g system_server run android hooking list classes | grep IWallpaperManagerCallback
, which works for me.
Or with quotes
objection -g system_server run "android hooking list classes" | grep IWallpaperManagerCallback
for better readability.
As per title, add extra optional argument for dumping class_methods and classes in filesystem files.
It would be nice if we could grep or somehow search in this output.