Closed Xefir closed 9 years ago
thanks for the report.
it seems that the NetoworkMonitor opens too many files and android goes crazy.
will fix when i port the NetworkMonitor into the core.
there is a way to solve this problem?
not again, i'm working on moving the code that trigger this issue into the core.
i'm almost done, few days i guess.
ok then I await your news :)
i found a problem that cannot be solved without modifying the pcap library.
sorry for the huge time required to fix this issue.
i'll update my Nexus 4 to lollipop as I fix the above error ( seems kernel-specific ).
then LG lollipop g3 there is no solution?
@minguccio86 I didn't say that i won't fix it.
i have to update my device to lollipop too ( i have a boring notification on my phone about that ), so i will certainly fix this issue.
but currently i'm busy with fixing the above one. I was just apologizing for the huge time i'm taking to fix this problem.
I run Lollipop @ my Nexus 5 and it's crashes too. Plesse keep up the great work. If it's possible to help Festung, I'm here ;)
@tux-mind ok thanks a lot then it will wait and thanks for your work
@tux-mind I noticed that the app (dsploit) is no more in playstore. there is news? has been replaced by some other app? thanks again for your support
I resolved, dsploit was replaced by Zanti and works on LOLLIPOP, here is the link for download : https://s3.amazonaws.com/zANTI/zANTI2.apk
What does that have to do with cSploit?
dsploi and zAnti are fusion
And still, what does that have to do with cSploit?
@xaitax The app is called dsploit and not csploit. The app has the same functions as Zanti dsploit also not crash on LOLLIPOP
You know this here is a cSploit page?
@xaitax feel we are talking about: '' dSploit as same as cSploit crash at start on Android 5.0 Lollipop ''. read the title, I close with this, if I can be of help was ok, good day
keep calm guys :laughing:
@minguccio86 dSploit has been merged into zANTI. i talked some week ago with evilsocket and him told me that android 5.0 it's full of crap and he spent a lot of time in fixing native code for being run over lollipop.
BTW, zANTI has nothing to do with cSploit. evilsocket is paid for working on zANTI. i received about 15 $ for all my work on cSploit.
even more they work 8 hours per day, while I have 1 hour per day from when my notebook broken up.
anyway a kindly guy purchased me an used thinkpad ( T60 ), it should arrive in my country in some days. when i receive it I can resume working while i'm in classroom.
sorry for the delay for fixing this issue, but the time i can send on this project it's drastically reduced because i can't work on it when i'm at school ( i'm writing from mobile now ).
thanks for your comprehension.
@miniguccio86 jaja, go play with your zanti, cSploit is still better.
ok I apologize. I realized my mistake now. I wait csploit be fixed for lollipop
+1 for this, i could really use this on my nexus 6
Hello everyone, we have news for csploit on lollipop?
This is a problem with android 5.0, must flash this file on recovery that u can download from here : "http://forum.xda-developers.com/attachment.php?attachmentid=3061976&d=1418466953" . before doing this you must completely delete csploit and all his component. it will help with the sniffing and Heart attack. enjoy
@erionialb I tried but nothing. does not work
[Android 'L'] Bypassing the new PIE security check http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page7 this is the page were i found the solution end with that flash all my sniffing tools started working again. i have a note 3 n9005 with android 5.0 touchwiz . have not tried on aosp
sorry for still inactive for so long, I spent holidays with my girlfriend's family, aware of my workstation.
@erionialb this issue is not related to the PIE error you talked about. PIE is only for dynamically linked executables. cSploit uses statically linked executables ATM.
working on it right now...
can someone test this pre-release apk ?
uninstalling or delete app data is not required.
thank you in advance :blush:
Oooops, wrong thread, sorry.
If it helps in anyway, that release still crashes on my Nexus 6 stock
FYI, this is exactly the problem I have currently with android 5.0.1
I don't understand how compile the two others repositories required to make cSploit work so I can't test to disable the keepAlive property.
Maybe you could test
@Xefir thanks for the hint!
please let me help you compiling the cSploit application, it's simpler than publish an apk for every attempt for fix this issue.
what repositories you can't compile ?
what is the content of build.log
?
thanks for your precious time.
When i want to do a make on this repo : https://github.com/cSploit/daemon
It gave me this :
gcc -g -O0 -Werror -Wall -I. -I../cSploitCommon -fPIC -c -o authenticator.o authenticator.c
authenticator.c:28:10: fatal error: 'logger.h' file not found
#include "logger.h"
^
1 error generated.
make: *** [authenticator.o] Error 1
Moreover, I don't know where I have to copy the two .so generated files after to include it on final apk
EDIT : I finally pointed the problem. You have to have the android-ndk and deal with readline on Mac OS.
Thanksfully I succeded to compile and run cSploit \o/
And my previous statement is wrong. In fact at several places, you have some FileInputStream and FileOutputStrem unclosed witch causes the Too Many Open Files here.
But it is not the main problem for Lollipop. The first error I have to fix is this :
5727-5773/org.csploit.android E/cSploitClient﹕ connect_unix: connect: No such file or directory
And I have absolute no idea where it goes =/
Hi @Xefir .
thanks for spending your time helping me fixing issues on cSploit.
long story short: if you use the make
command you will compile cSploitd for your PC, not for Android.
for compiling the native stuff open a terminal and
cd /path/to/cSploit/repo/cSploit/jni/
./build.sh
if some problem occurs post the content of /path/to/cSploit/repo/cSploit/jni/build.log
.
it will build all the native stuff ( will take a lot the first time ), and make the core
package containing the daemon and some required tools like nmap, ettercap and so on.
after that, open android studio
Open Existing Project > /path/to/cSploit/repo/settings.gradle
> Use gradle wrapper
if it asks about an existing project choose "Delete and Import".
then: Run > Run
it will install cSploit on your device ( you have to reinstall it the first time ).
How do you known that there is many unclosed FileStreams ? can you point me out the code ? thanks :blush:
Download the app SELinux mode changer in playstore and change the SELinux mode of enforcing to Permissive and restart the device, uninstall and reinstall the csploit.
@fabinhojcr that doesn't work on nexus 6 lollipop 5.0.1
finally I switched from network discovery
to network-radar
.
this should also fix the EMFILE
bug, which affect lollipop devices.
now that i reached a stable state with network-radar
I can upgrade my device to lollipop too :blush:
please test latest release ( 1.3.0 ) and let me known the results :wink:
@tux-mind tested on Nexus 6 5.0.1 Lollipop, it initializes, asks for root and then pops up with:
Initialization Error heart attack!
@SaggySally thanks for tried it out so fast!
can you provide a logcat ?
it will be perfect if you can also provide /data/data/org.csploit.android/files/cSploitd.log
.
thanks in advance :blush:
@tux-mind Many thanks for your great work, below you find the logcat: build.board: shamu build.bootloader: 0x7105 build.brand: google build.cpu_abi: armeabi-v7a build.cpu_abi2: armeabi build.device: shamu build.display: LRX22G build.fingerprint: google/eos_shamu/shamu:5.0.2/LRX22G/david01250615:userdebug/test-keys build.hardware: shamu build.host: kofftop build.id: LRX22G build.manufacturer: motorola build.model: Nexus 6 build.product: eos_shamu build.radio: unknown build.serial: ZX1G4224FG build.tags: release-keys build.time: 1422188158000 build.type: userdebug build.user: david version.codename: REL version.incremental: eng.david.20150125.061209 version.release: 5.0.2 version.sdk_int: 21
01-26 11:05:56.273 E/AndroidRuntime(21365): Process: org.csploit.android, PID: 21365 01-26 11:05:56.273 E/AndroidRuntime(21365): at org.csploit.android.MainActivity$2$1.run(MainActivity.java:359) 01-26 11:06:01.674 E/AndroidRuntime(21499): Process: org.csploit.android, PID: 21499 01-26 11:06:13.222 I/DEBUG (8418): pid: 21799, tid: 21821, name: RenderThread >>> org.csploit.android <<< 01-26 11:06:23.406 I/DEBUG (8418): pid: 22062, tid: 22084, name: RenderThread >>> org.csploit.android <<< 01-26 11:06:35.976 I/DEBUG (8418): pid: 22488, tid: 22510, name: RenderThread >>> org.csploit.android <<< 01-26 11:07:01.831 I/DEBUG (8418): pid: 23578, tid: 23600, name: RenderThread >>> org.csploit.android <<< 01-28 14:28:26.365 W/FileUtils(9786): Failed to chmod(/storage/emulated/0/Boat_Browser_Free/downloads/cSploit-release-6.apk): android.system.ErrnoException: chmod failed: EPERM (Operation not permitted) 01-28 14:28:28.096 I/ActivityManager(995): START u0 {act=android.intent.action.VIEW dat=file:///storage/emulated/0/Boat_Browser_Free/downloads/cSploit-release-6.apk typ=application/vnd.android.package-archive flg=0x10000000 cmp=android/com.android.internal.app.ResolverActivity} from uid 10117 on display 0 01-28 14:28:30.957 I/ActivityManager(995): START u0 {act=android.intent.action.VIEW dat=file:///storage/emulated/0/Boat_Browser_Free/downloads/cSploit-release-6.apk typ=application/vnd.android.package-archive flg=0x13000000 cmp=com.android.packageinstaller/.PackageInstallerActivity} from uid 10117 on display 0 01-28 14:28:42.721 I/ActivityManager(995): START u0 {dat=file:///storage/emulated/0/Boat_Browser_Free/downloads/cSploit-release-6.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from uid 10044 on display 0 01-28 14:28:42.784 W/InstallAppProgress(28718): Replacing package:org.csploit.android 01-28 14:28:43.184 D/Finsky (16956): [1] WorkerTask.onPreExecute: Verification Requested for id = 7, data=file:///storage/emulated/0/Boat_Browser_Free/downloads/cSploit-release-6.apk flags=18 fromVerificationActivity=false 01-28 14:28:45.014 D/DefContainer(28756): Copying /storage/emulated/0/Boat_Browser_Free/downloads/cSploit-release-6.apk to base.apk 01-28 14:28:45.705 D/PackageManager(995): Renaming /data/app/vmdl1178234289.tmp to /data/app/org.csploit.android-2 01-28 14:28:45.710 I/ActivityManager(995): Force stopping org.csploit.android appid=10181 user=-1: uninstall pkg 01-28 14:28:45.864 I/PackageManager(995): Package org.csploit.android codePath changed from /data/app/org.csploit.android-1 to /data/app/org.csploit.android-2; Retaining data and using new 01-28 14:28:45.887 I/art (995): DexFile_isDexOptNeeded failed to open oat file '/data/dalvik-cache/arm/data@app@org.csploit.android-2@base.apk@classes.dex' for file location '/data/app/org.csploit.android-2/base.apk': Failed to open oat filename for reading: No such file or directory 01-28 14:28:45.887 I/art (995): DexFile_isDexOptNeeded failed to open oat file '/data/app/org.csploit.android-2/arm/base.odex' for file location '/data/app/org.csploit.android-2/base.apk': Failed to open oat filename for reading: No such file or directory 01-28 14:28:45.887 I/PackageManager(995): Running dexopt on: /data/app/org.csploit.android-2/base.apk pkg=org.csploit.android isa=arm vmSafeMode=false 01-28 14:28:45.934 I/dex2oat (28778): /system/bin/dex2oat --zip-fd=6 --zip-location=/data/app/org.csploit.android-2/base.apk --oat-fd=7 --oat-location=/data/dalvik-cache/arm/data@app@org.csploit.android-2@base.apk@classes.dex --instruction-set=arm --instruction-set-features=div --runtime-arg -Xms64m --runtime-arg -Xmx512m 01-28 14:28:48.303 I/ActivityManager(995): Force stopping org.csploit.android appid=10181 user=-1: update pkg 01-28 14:28:48.304 W/PackageManager(995): Code path for pkg : org.csploit.android changing from /data/app/org.csploit.android-1 to /data/app/org.csploit.android-2 01-28 14:28:48.304 W/PackageManager(995): Resource path for pkg : org.csploit.android changing from /data/app/org.csploit.android-1 to /data/app/org.csploit.android-2 01-28 14:28:48.521 I/ActivityManager(995): Force stopping org.csploit.android appid=10181 user=0: pkg removed 01-28 14:28:48.681 D/BackupManagerService(995): Received broadcast Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:org.csploit.android flg=0x4000010 (has extras) } 01-28 14:28:49.982 D/BackupManagerService(995): Received broadcast Intent { act=android.intent.action.PACKAGE_ADDED dat=package:org.csploit.android flg=0x4000010 (has extras) } 01-28 14:28:49.993 W/BackupManagerService(995): Removing schedule queue dupe of org.csploit.android 01-28 14:28:50.244 I/ConfigFetchService(3068): PackageReceiver: Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:org.csploit.android flg=0x4000010 cmp=com.google.android.gms/.config.ConfigFetchService$PackageReceiver (has extras) } 01-28 14:28:50.304 I/ConfigFetchService(3068): onStartCommand Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:org.csploit.android cmp=com.google.android.gms/.config.ConfigFetchService (has extras) } 01-28 14:28:50.342 D/PackageBroadcastService(3068): Received broadcast action=android.intent.action.PACKAGE_REMOVED and uri=org.csploit.android 01-28 14:28:53.460 I/ActivityManager(995): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=org.csploit.android cmp=org.csploit.android/.MainActivity} from uid 10044 on display 0 01-28 14:28:53.510 I/ActivityManager(995): Start proc org.csploit.android for activity org.csploit.android/.MainActivity: pid=28974 uid=10181 gids={50181, 9997, 3003, 1028, 1015} abi=armeabi 01-28 14:28:53.867 D/CSPLOITcore.System.init: initializing System... 01-28 14:28:54.148 D/CSPLOITcore.System.isARM: Build.CPU_ABI = armeabi-v7a 01-28 14:28:54.149 D/CSPLOITcore.ToolsInstaller.needed: Checking version file /data/data/org.csploit.android/files/tools/VERSION 01-28 14:28:54.151 D/CSPLOITcore.ToolsInstaller.install: Installing tools ... 01-28 14:28:54.152 D/CSPLOITcore.System.setForwarding: Setting ipv4 forwarding to false 01-28 14:28:54.157 E/cSploitClient(28974): start_command: not authenticated 01-28 14:28:54.158 E/CSPLOITcore.System.setForwarding: cannot start commands 01-28 14:28:54.158 E/cSploitClient(28974): connect_unix: connect: No such file or directory 01-28 14:28:54.649 I/ActivityManager(995): Displayed org.csploit.android/.MainActivity: +1s157ms 01-28 14:28:55.969 I/ConfigFetchService(3068): PackageReceiver: Intent { act=android.intent.action.PACKAGE_ADDED dat=package:org.csploit.android flg=0x4000010 cmp=com.google.android.gms/.config.ConfigFetchService$PackageReceiver (has extras) } 01-28 14:28:56.098 I/ConfigFetchService(3068): onStartCommand Intent { act=android.intent.action.PACKAGE_ADDED dat=package:org.csploit.android cmp=com.google.android.gms/.config.ConfigFetchService (has extras) } 01-28 14:28:56.202 E/cSploitClient(28974): connect_unix: connect: No such file or directory 01-28 14:28:56.239 D/PackageBroadcastService(3068): Received broadcast action=android.intent.action.PACKAGE_ADDED and uri=org.csploit.android 01-28 14:28:56.257 I/UpdateIcingCorporaServi(27618): Updating corpora: APPS=org.csploit.android, CONTACTS=MAYBE 01-28 14:28:57.034 D/PackageBroadcastService(3068): Received broadcast action=android.intent.action.PACKAGE_REPLACED and uri=org.csploit.android 01-28 14:28:58.945 D/SCREEBL (5319): ---> SCREEBL Package Upgraded: package:org.csploit.android 01-28 14:29:03.326 D/CSPLOITcore.System.startCoreDaemon: 'ACCESS GRANTED' found 01-28 14:29:03.326 W/CSPLOITcore.System.startCoreDaemon: STDERR: error: only position independent executables (PIE) are supported. 01-28 14:29:03.327 E/CSPLOITMainActivity$5.run: core daemon returned 1 01-28 14:29:11.758 D/CSPLOITcore.System.setForwarding: Setting ipv4 forwarding to false 01-28 14:29:11.759 E/cSploitClient(28974): start_command: not authenticated 01-28 14:29:11.759 E/CSPLOITcore.System.setForwarding: cannot start commands 01-28 14:29:11.759 D/CSPLOITcore.System.clean: Releasing locks. 01-28 14:29:31.201 I/ActivityManager(995): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.csploit.android/.MainActivity (has extras)} from uid 10022 on display 0 01-28 14:29:31.329 D/CSPLOITcore.System.isARM: Build.CPU_ABI = armeabi-v7a 01-28 14:29:31.329 D/CSPLOITcore.ToolsInstaller.needed: Checking version file /data/data/org.csploit.android/files/tools/VERSION 01-28 14:29:31.330 E/cSploitClient(28974): connect_unix: connect: No such file or directory 01-28 14:29:31.510 I/ActivityManager(995): Displayed org.csploit.android/.MainActivity: +253ms 01-28 14:29:31.627 D/CSPLOITcore.System.startCoreDaemon: 'ACCESS GRANTED' found 01-28 14:29:31.627 W/CSPLOITcore.System.startCoreDaemon: STDERR: error: only position independent executables (PIE) are supported. 01-28 14:29:31.627 E/CSPLOITMainActivity$5.run: core daemon returned 1 01-28 14:29:33.624 D/CSPLOITcore.System.setForwarding: Setting ipv4 forwarding to false 01-28 14:29:33.624 E/cSploitClient(28974): start_command: not authenticated 01-28 14:29:33.624 E/CSPLOIT[core.System.setForwarding](289
ok, I have to fix the PIE bug. I have to think a smart way to not ship different binaries in the same package. putting both PIE and not-PIE executables inside cSploit will double it's size.
will work on it in the next week, I have to study physics now :pensive:
Sorry, I had autospelling errors in my first post and have edited it :-) Sounds like a great approach. Do you think that the pie fix posted above from @erionialb could work? Best luck for physics!
The answer to my question is no. If you install the first fix in the link then you will get stuck in boot and the second fix doesn't work either. :-)
Good news: i just installed 5.0.1 :sunglasses:
@alexmanner the solution to the PIE error is to have ALL native executables in PIE format.
many apps have both in PIE and not-PIE, then select the one to use on runtime. cSploit binaries require up to 20MB and I hate apps that require too much space on my device.
I think that a good solution is to use something like http://update.csploit.org/android/core.zip
and appending a list of per-platform settings.
some examples:
http://update.csploit.org/android/core.zip?PIE=0
http://update.csploit.org/android/core.zip?static=1
and so on...
any other suggestion ?
the drawbacks of this solution is that an internet connection is required on first installation.
PIE: core fixed.
next steps:
other problems with lollipop:
thanks for waiting all this time. sorry if I could't update my device before, but i preferred fix a bug on my previous ROM, thus to increase app compatibility.
@tux-mind When will dsploit apk Will be available
I am talking about the new update For lollipop !!
Never ask for ETA :laughing: BTW I'm choosing how to fix the PIE error .
There are three choices:
I don't want to lost support for older devices. So the last option isn't the right one.
I have to look out if the PIE loader works even of devices with different processor ( e.g. armv7a binaries on armv5t platform ), I bet it will not.
To check it out I have to make some tests.
Probably the 2 different packages solution is the right one.
The design phase is the most delicate one :wink:
@tux-mind Many thanks again for all your work and that you share your work with the public. This is very much appreciated. I happy to hear that you have migrated to Android 5.x. Regarding the disk space the application requires, this is totally irrelevant for me since I still have 22 GB free disk space. But I understand that there are people for who disk space might be an issue.
Great to hear that you have identified the core issues with Android 5.x compatibility.
Hey tux, any progress on fixing the app for Lollipop?
Hi !
dSploit as same as cSploit crash at start on Android 5.0 Lollipop. Here is my logcat :
If you have an idea ^^" Thanks :-)