Denis Efremov

No, I didn't test on Android 8.1 Probably, it works on 8.1

This means that adbd is not starting. Reasons could be different. What android version? What phone, firmware? Does it work if you switch selinux to permissive mode?

> I wonder if something like frida/frida#877 (comment) would work. No, it won't work. SELinux (most probably) kills adb root because this policy https://github.com/evdenis/adb_root/blob/master/sepolicy.rule is not enough on Samsung SM-G900F,...

That's why I wrote "(most probably)". I don't know the exact reason on your phone and obviously can't debug it. I only know that SELinux can kill the process or...

The way you fixed your problem with starting adbd manually is another "indirect evidence" for me that you struggle with SELinux, because I also faced the exactly the same behaviour...

Just in case, if you use LineageOS you don't need this module since it's possible to switch adbd root in settings.

Thanks for the report. I fixed a crash with https://github.com/evdenis/cvehound/commit/f01aa834fc1271cb3e53ab4c068a790fe377c7fd Regarding wrong architecture detection (and kvm/xen cves reported even if they are not enabled in .config). I know about this...

I pushed yesterday 2 commits and the second one was to handle this problem https://github.com/evdenis/cvehound/commit/040ae5d500d6c30078df1a03bc9c3e6878c1d11c How did you install the tool?

> Will ENOKEY be returned for all subsequent filesystem operations? Or why will it result in "lost connection"? Yes, for all subsequent "write" filesystem operations. > What is the additional...

> How hard is it to do? What what does it involve? 1. Generate keys in create-image.sh ``` $ dd if=/dev/urandom bs=1 count=32 status=none | keyctl padd user kmk-user @u...