CFC4N

I think this may not be related to eCapture; if you need it, you can open it. Feel free to share your new findings.

In the source code of the library, it can be seen that it uses a custom TLS handshake packet, instead of the official implementation by golang. https://github.com/bogdanfinn/tls-client/blob/077a497dc1047d3ed5f53f257af383b334a7a609/roundtripper.go#L154 ```golang conn :=...

It works.

Please provide more up-to-date information. For example, your system version, kernel version, CPU architecture, and so on.

Apologies, there is no Armbian testing environment available, and I also lack the energy to support these niche environments; please troubleshoot it yourself.

Which TLS encryption library does WebRTC use? Is it OpenSSL? upload `ldd /path/webRTC` output here.

eCapture currently only supports key capture for `openssl`, also known as `libssl.so`, and does not temporarily support key capture for `gnutls` or other libraries. You need to first determine which...

ping @sergey-safarov

1. He can work normally. However, you need to search for the offer offset of the hooked function, manually enter it into the program, and then compile the program. https://github.com/gojue/ecapture/blob/4b1c52df6a935886058f08aff3b7acd2e60a872c/user/module/probe_openssl_text.go#L47C3-L52C6...

`20` is more accurate than `18`. ```c enum tls12_server_hs_state_t { state12_start_accept = 0, state12_read_client_hello, state12_read_client_hello_after_ech, state12_cert_callback, state12_tls13, state12_select_parameters, state12_send_server_hello, state12_send_server_certificate, state12_send_server_key_exchange, state12_send_server_hello_done, state12_read_client_certificate, state12_verify_client_certificate, state12_read_client_key_exchange, state12_read_client_certificate_verify, state12_read_change_cipher_spec, state12_process_change_cipher_spec, state12_read_next_proto, state12_read_channel_id,...