-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kern: Adjust the timing of key acquisition to distinguish between TLS #576
Conversation
… versions * The best way is to first determine the current SSL mode, whether it is server or client. Currently, * the ssl->server field is of bool type, and using the offsetof method is not very readable. * Therefore, the minimum value of the state is temporarily used instead. * The judgment mechanism for TLS 1.3 follows the same approach. Signed-off-by: CFC4N <[email protected]>
你可以帮忙测试一下吗?使用非Android的boringssl类库,测试一下这个PR是否能正常捕获密钥。 分别以Server\Client两种模式,测试TLS 1.2、1.3的情况,谢谢。 Can you help test this? Using the non-Android boringssl library, check if this PR can properly capture the key. Test in both Server and Client modes for TLS 1.2 and 1.3 scenarios, thank you.
|
辛苦了,我这周来搭环境验证 |
上述4种场景都验证了,都可以取到key了 All four scenarios have been verified and the key can be obtained. |
pcapng包里,可以正常看到解密后的明文文本吗? In the pcapng file, can you normally see the plaintext text after decryption? |
pcap的包 4种情况也都验证通过 The pcap packets have successfully passed all four tests. |
最好的办法是先判断当前SSL的模式,是server还是client。 目前ssl->server 字段是bool类型,offsetof方法不太好读取,暂时使用state的最小值代替, 下面 TLS 1.3的判断机制也是这样。
The best way is to first determine the current SSL mode, whether it is server or client. Currently, the ssl->server field is of bool type, and using the offsetof method is not very readable. Therefore, the minimum value of the state is temporarily used instead. The judgment mechanism for TLS 1.3 follows the same approach.