ver 0.8.9 can`t work on android kernel 6.1.99 , but ver 0.6.1 did work

[r0ysue]

ver 0.8.9 can`t work on android kernel 6.1.99 , but ver 0.6.1 did work
tried -b 0/1/2 all failed

./ecapture tls -b 1 -p 11515 --hex
should capture all the traffic but nothing showed off

tried version 0.6.1 that works fine

Linux Server/Android (please complete the following information):

• Device: [Pixel 6]
• Env:androidgki_aarch64:0.6.1-20230716-e1cd6c7:[CORE]
• OS: Android 14 AP1A.240505.004
• Arch: Linux localhost 6.1.99-android14-11-gd4dab27b9d1c-dirty 5.10.101 not support #1 SMP PREEMPT Thu Oct 3 20:50:04 UTC 2024 aarch64 Toybox
• Kernel Version: 6.1.99

[cfc4n]

Try using --ssl_version="boringssl 1.1.1" flag.

[r0ysue]

nothing happens ...

[xxxxxliil]

把关于设备的页面发一下看看

[r0ysue]

[xxxxxliil]

0.7.0 可以获取 keylog 吗

[NPC2000]

Try using --ssl_version="boringssl 1.1.1" flag.

佬，我之前提的问题应该也是和这个情况一样的，用0.61版本就可以抓到https报文，我内核是6.1.57

#622

[irabbit666666]

Versions 0.8.12 and 0.9 still don't work properly

[irabbit666666]

0.6.1 can work，but i want the higher version

[NPC2000]

在最新版上会报错

[cfc4n]

没有相关硬件设备，无法重现。

[cfc4n]

@dosu

[dosubot]

Hello, @cfc4n! I'm here to help you with any issues you're facing. If you need assistance with bugs, have questions, or want to become a contributor, I'm here to assist you while waiting for a human maintainer.

It seems that there are issues with eCapture version 0.8.9 on Android kernel 6.1.99, while version 0.6.1 works fine. A similar issue was discussed in a GitHub issue where users faced challenges capturing HTTPS packets on an Android device with kernel version 6.1.57. They suggested using the --ssl_version="boringssl 1.1.1" flag, which might help resolve SSL-related errors [[id=622]].

Additionally, eCapture utilizes eBPF to capture SSL/TLS traffic by hooking into specific functions in OpenSSL/BoringSSL libraries. Potential points of failure could include kernel version compatibility, library version detection, and eBPF program loading issues ^[1].

If the --ssl_version flag does not resolve the issue, it might be worth checking if the correct libraries are being hooked and ensuring compatibility with the specific kernel and library versions on your device.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}