Heartattack about android HOT 35 CLOSED

Every time I start I get this error

from android.

Did you tried to fully reinstall csploit or reboot your phone?

from android.

I know what the problem is now. Every time I Grant SuperSU access I get that error.

from android.

Here is my logcat http://pastebin.com/T88ubkyC

from android.

Do you use Lollipop (Android 5.0)?

from android.

@DominikTV I am using ARHD 82.0 Android 4.4.3 HTC one m7

from android.

Client cannot connect to cSploitd-Daemon:
E/cSploitClient(10485): connect_unix: connect: No such file or directory

Attatch the file Android/data/org.csploit.android/files/cSploitd.log on your sdcard, please.

from android.

https://mega.co.nz/#!BpFyxKpT!OJ6A3Im37d10LktE8VVI0xM0x19kwfrW_kFF833unjw

from android.

@Systemad you sent the wrong file, is cSploitd.log not cSploitd.

please report if the file is not present.

as the name say, nightly builds are not stable,
in fact i still have to test the changes made by @cmayer0087 .

i'm almost done with the network-monitor ( i'm developing a workaround for a kernel problem 😲 ), after this i'll resume working on the Java side and fix this issue too.

from android.

The log file doesn't exits. I have looked both on /Android/data/org.cSploit.Android/files. And data/data/org.cSploit.Android

from android.

if this file doesn't exists it's likely, that the cSploit-daemon was not restarted.
Restart your Phone and try again, please.

from android.

I did, and I am using multirom and so I tried on CM11 (in case if it was my ROM) and got same error.

from android.

And still no cSploitd .log

from android.

Sorry guys, there will some building issues on the server and I was busy within flights.. I will manually built the nightly in a few minutes. But it will only fix the commit on 30th of November as there is nothing new.
Cheers.

from android.

same here...

from android.

I have bought a tablet, on which the same issue occurs. Files don't have execution permission on the sdcard. The first option is to remount the sdcard with the proper permissions. The second is to find a directory whereto we could move the stuff. Maybe we shoud create a dictionary in /system like BusyBox does. What do you think @tux-mind ?

from android.

Same issue occurs on CM11, old files location (/data/data/org.csploit.android/files) seems to work correctly though. Isn't remounting sdcard with exec some kind of a security risk?

from android.

it is. 👍

from android.

had this issue on cm11. had to change permissions on csploitd in /data/media/0/Android/data/org.csploit.android/files
file.setExecutable(true, false); in the tools installer apparently didn't really do anything.

from android.

@cmayer0087 changing mount flags of /sdcard is totally unacceptable.
it's an huge security risk.

why did you put the daemon on the sdcard ?

from android.

@bionictrip fat32 doesn't support linux permissions, so you can't set it per file.

@tux-mind because on galaxy-devices a binary isn't allowed to use fork if it is under the /data directory:
https://github.com/gokulnatha/GT-I9500/blob/master/arch/arm/kernel/sys_arm.c#L175
Thats why #1 occured on my device.

Using for example /system/csploit will fix both #1 and this issue, but that directory isn't auomatically deleted on deinstallation of csploit.

from android.

here, the /data/data/org.csploit.android/files directory is empty, which results in some ENOENT errors. (also CM11 on Samsung Galaxy S3)

from android.

another idea may be bind mount (if thats possible on android?) to another directory (is /system the only choice?)
afaik /system stuff is usually deployed using update.zip archives + recovery bootloader.

is fork() really necessary? :-)

from android.

The partitions except /system, /data and sdcard are not destined to contain much data or binaries or doesn't exists on every device.

Bind mount is an interesting idea.

Yes we really need fork 😃

from android.

Fork seems only be restricted if the process is executed as root. If the daemon is executed under as non root user, the daemon should be allowed to use fork. I will check that.

from android.

How about creating a loop file system on the sdcard or in the data dir, and mounting that inside the sdcard? I have no idea if this would work, or how linux mount options work with inheritance (or whatever), but I know that Linux Deploy works fine for me and I think it does something like this with a chroot. I've been considering using Kali on Linux Deploy instead of csploit, but then I don't get a nice android GUI.

from android.

@cmayer0087 why the su binary could execute /data/data/org.csploit.android/files/cSploitd in previous versions ?

from android.

@Efreak it may works, but it's a tricky way to work.

from android.

@cmayer0087 we need root privileges. every child that we spawn need them.

from android.

@cmayer0087 i reverted your commit that moves executables from /data to /sdcard .

we need to study another way to fix #1 , let's talk on it.

i made a new branch that track the repo before i reverted your stuff.

from android.

that fixed the issue for me

from android.

@rigid thanks for the feedback.

if anyone else still have this problem please reopen it.

i will pay more attention on pull requests, sorry for the inconvenience guys.

from android.

I am still getting this on the latest nightly and release, Nexus 5 on CM12. http://pastebin.com/hEumYbEX
I notice two things in this log: 1. The socket it is looking for does not exist (I double checked /dev/socket) 2. Only PIE execs are supported, meaning we can't just run a native binary out of any directory. This will be a problem for anybody on Android L.

from android.

@keaneokelley thanks for the report.
building it statically will fix the issue, but will increase binary size.

since the daemon it's a long-lived process i prefer to provide 2 different versions of the binaries.

please open a new issue so i can refer to that one.
this is related to an old mistake i made with a pull request.

from android.

@keaneokelley nevermind, it has already been reported in #18 .

will fix ASAP.

from android.