Implement old drozer-agent detection
cyberMilosz opened this issue · 1 comments
cyberMilosz commented
We've seen multiple issues stemming from people accidentally running drozer 2's agent on the device. This should be easy enough to detect from the console - see if we can resolve com.mwr.dz.Agent
(rather than com.WithSecure.dz.Agent
). If this does work, the user should be informed of the mismatch and linked directly to the drozer-agent GitHub repo.
cyberMilosz commented
Even better - just catch the exception