-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Discuss #64
Comments
clean up your file in peterpt/thefatrat , like log,bug and trash . i will download your files and uploads som files to my github . this open source dude , we can work together for develop this why you put createapk in outside ? i suggest put create apk on /tools and give alias maybe i will fix some function and variable if you done with ( clean up log,bug and trash ) |
Hi , thanks for pointing out the log folder , somehow when i updated the last time i forgot to clean that folder . i already cleared the log folder , all other folders are from fatrat originally except : **Important : ** |
Just another thing , if you find any bug on my changes then let me know , because from this minute i could not found any error executing fatrat or any of its current scripts or even the new apkcreate script . The changes i made in last 15 minutes where the only minor bugs i found in apkcreate where path variable was not written properly for that script current path variable set . |
sorry for last hour changes , i just had to update readme.md in main directory because pictures were still from 1.8 version , and i also updated the tutorial video link related to how to create a rat apk . |
will be update |
i know , but now i got another idea to implement . |
ok , on my git , zenity will popup from now on everytime user selects an apk rat . This idea just came up this morning to implement , and it is finished . |
dont use zenity to much { Graphic user interface ) , why im not using gui in located file and set flhost ? because i want thiss tool >> old school style . |
if you want create that , sure no problem . but . i suggest you , when you use use zenity for another features .the tools iits noot beatiful again :p |
yeah , i know . |
android-sdk-25 ( larger file ? am i right ? |
yes , and that folder contains sub-folders with libraries and all the android tools , so apktool does not have to depend on system old incompatible tools . Android build tools on kali repository is still on 23 the same thing happens to debian sid repo : because jessie repository is still on version 20 So , they will first go to version 24 and then after sometime they will go to 25 witch is the version we use . |
200 mb ? |
android-sdk-25 : 246Mb the reason why android sdk is so big is because an apk is not for only a particular device or resolution . Anyway , if users install this package from apt , it will be downloaded from google or any other mirror because of its size . look here at the file tools_r25.2.5-linux.zip in one of the android repositories . I had i comply with backdoor-apk requirements used by dana james at his github . one of the other reasons why it is so big , it is because proguard interacts with the compiled apk , and proguard requires the file "android.jar" witch is not in build tools but it is in sdk , and this is why the folder is so big in size . and look here the call for that file in proguard config , line 15 in the original project : the original script is from him and i just adapted it to fatrat directory structure and tools paths . |
add in main fatrat folder on the readme.md the credits to : also , remove the docker , because it will not work if user relies on docker to install fatrat , without running setup.sh the config.path will be not created , and if config.path is not created then nothing will work and every script in fatrat will say to user execute setup.sh Change picture of fatrat on readme.md , the current picture is still at 1.8 version . you did considerable changes in setup.sh . You are mixing apktool2.2.2 with an aapt tool from android 23 (in case user have some installed on his system) , where dx is from 25 . You should get in consideration the fact that when i rebuild the setup script , i did it thinking that user may have or not a kali system installed , while you considered that every user that will use fatrat is using a pentest distribution . One of these things will happen on the next days or weeks when users start to clone the git and using it :
the thing is that i write a variable path for aapt in config.path , but in reality that variable is never called in any script . Well ..... , we will know in the bugs in future . |
lets discuss in email dude , this issue will be close |
I was unable to create the pull request from my git to yours because there are massive changes in my git that crashes my firefox when git is analyzing the differences .
FatRat is originally your creation , so in good faith i believe that i should send you a pull request everytime some good changes are made .
FatRat becomes FatRat 1.9beta
and the changes are :
APK (5) rat rebuild totally changed .
(adapted backdoor-apk script to fatrat to both work together)
APKS have a new payload hiding method in rat apk to not be detected .
Apktool will not be installed no more by setup.sh , the same thing applies to : dx , zipalign
(apktool on debian repo is 2.2.1 , and that version have a bug that gives error on compiling the apks , so , apktool and android tools were updated to latest version 25.0.2 and embeded in (tools) directory of fatrat .
Some other changes were made but i can not remember everything now because i have been doing the changes since beginning of last week .
The only way that i see for you to merge my git to yours is :
-cloning my git to your hard disc
-Enter hidden directory .git in my git and change from :
https://github.com/peterpt/TheFatRat
to
https://github.com/Screetsec/TheFatRat
and then over the terminal do a git push to your account , so all files can be changed .
If you do not want to merge then there is no problem .
Anyway , here are the new changes
https://www.youtube.com/watch?v=Nj7AFEBjvdQ
The text was updated successfully, but these errors were encountered: