You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lots of Installation-guide.md seems obsolete to me, but I am not sure so not modifying.
Device requirements :
Download and install Frida-server on the device
To my understanding, this is obsolete and Frida-server is automatically uploaded to the device.
Pull/build the dependencies: not clear to me. Would probably say that either you install from package: npm install -g dexcalibur, or grab the sources and build with npm install -g?
3 Configure: to my understanding, you need not do this any longer, this is done at setup stage on the web ui. I am not event sure config.js still exists. I see there is a .dexcalibur/config.json, but not exactly with the same settings.
4 Run: to my understanding, frida-server on the device should automatically start, and the end-user should not need to do this manually?
5 (OPTIONAL): to my understanding, this is handled by the Web UI now.
If you agree + have comments, I can prepare a pull request for this if you like.
The text was updated successfully, but these errors were encountered:
On most of points, except (4) , you are right. Documentation should be clarified.
About (3), since Dexcalibur can be installed through NPM, configuration file is now stored only into '~/.dexcalibur/' folder. This file contains the path of dexcalibur workspace. Others settings are stored into Dexcalibur's workspace.
About (4), Dexcalibur tries to manage 'frida-server' when it has been uploaded on device by Dexcalibur. However, there some cases where it is not possible because tool is not aware of the location or has not right to spawn it. Actual version of Dexcalibur not provides easy way to edit location. Unsupported case where user needs to start 'frida-server' and where 'frida-server' status cannot be retrieved :
if you set a custom name for frida-server binary
if you move frida-server at a custom location
if you use another way to inject frida
Of course any contributions are welcome 😃 , but be aware i fully rewrote Dexcalibur engine and added a new UI. I plan to make a comemrcial version. Dexcalibur will be always free and open-souce, but i develop additionnal commercial features.
Lots of
Installation-guide.md
seems obsolete to me, but I am not sure so not modifying.To my understanding, this is obsolete and Frida-server is automatically uploaded to the device.
Pull/build the dependencies: not clear to me. Would probably say that either you install from package:
npm install -g dexcalibur
, or grab the sources and build withnpm install -g
?3 Configure: to my understanding, you need not do this any longer, this is done at setup stage on the web ui. I am not event sure
config.js
still exists. I see there is a.dexcalibur/config.json
, but not exactly with the same settings.4 Run: to my understanding, frida-server on the device should automatically start, and the end-user should not need to do this manually?
5 (OPTIONAL): to my understanding, this is handled by the Web UI now.
If you agree + have comments, I can prepare a pull request for this if you like.
The text was updated successfully, but these errors were encountered: