Skip to content
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

feat(frida) upgrade to frida 15.x and frida-tools 10.x #473

Closed
wants to merge 3 commits into from

Conversation

hazcod
Copy link

@hazcod hazcod commented Jul 23, 2021

No description provided.

@hazcod hazcod changed the title feat(frida) upgrade to frida 15.x feat(frida) upgrade to frida 15.x and frida-tools 10.x Jul 26, 2021
@hazcod hazcod mentioned this pull request Jul 26, 2021
@leonjza
Copy link
Member

leonjza commented Jul 26, 2021

hey! thanks for this pr! i'm blocked at the moment pending a rework of the spawning logic i mentioned here #456 (comment). will create a ticket to track the work.

@leonjza
Copy link
Member

leonjza commented Jul 26, 2021

created #474 to track

leonjza added a commit that referenced this pull request Oct 25, 2021
this commit contains many changes. the most important of which
is a completely rewritten Agent class, improving support for
early instrumentation.

pre this commit, because we we're injecting the frida gadget in
target applications, we expected communications to occur over
a tcp socket. as far back as frida 12.7+ support injecting the
frida-server into applications that are debuggable vastly
simplifies this process in jailed environments. as such, we can
use normal "usb" comms, and thereby more closely follow the
same logic as found in frida-* tools.

a small changelog for all the changes:

- remove the get_device_info() call that relied on frida scripts
  to get information about the platform. instead we're now using
  device.query_system_parameters()
- replace the old `explore` command with a new `start` command
- support spawning new applications
- support attaching to the frontmost application
- support enabling the node debug port, accessible via the chrome
  debugger
- support immediately resuming apps
- replace os with pathlib in some places
- remove the `objection device_type` command
- add the `resume` repl command to resume apps
- add a prompt token to show the current process state (pause/run)

no tests were fixed, so expect most of them to fail :P

related issues: #473, #474
@leonjza leonjza closed this in bf31a43 Feb 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants