![]() ![]() Ssl_dissect_hnd_hello_common found SERVER RANDOM -> state 0x12 Ssl_try_set_version found version 0x0303 -> state 0x10ĭecrypt_ssl3_record: app_data len 61, ssl state 0x10ĭissect_ssl3_handshake iteration 1 type 2 offset 5 length 57 bytes, remaining 66 Record: offset = 0, reported_length_remaining = 1448 Ssl_dissect_hnd_hello_common found CLIENT RANDOM -> state 0x01Ĭonversation = 0x563e9bbade10, ssl_session = 0x563e9bbadee0 Record: offset = 0, reported_length_remaining = 224ĭissect_ssl3_record: content_type 22 Handshakeĭecrypt_ssl3_record: app_data len 219, ssl state 0x00ĭecrypt_ssl3_record: using client decoderĭecrypt_ssl3_record: no decoder availableĭissect_ssl3_handshake iteration 1 type 1 offset 5 length 215 bytes, remaining 224 Packet_from_server: is from server - FALSEĬonversation = 0x563e9bbad2f0, ssl_session = 0x563e9bbad3c0 Ssl_init port '443' filename '/home/user/.mitmproxy/new_ca/mitmproxy-ca.pem' password(only for p12 file) ''Īssociation_add ssl.port port 443 handle 0x563e9a945210 Ssl_init private key file /home/user/.mitmproxy/new_ca/mitmproxy-ca.pem successfully loaded. Ssl_association_remove removing UDP 443 - handle 0x563e9a945210 Some excerpts of Wireshark’s SSL log (entire file here: ): Wireshark SSL debug log The cipher TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is used, but I found that it is supposed to work if sslkeylogfile.txt is provided. I configured wireshark to use the mitmproxy-ca.pem file and the file sslkeylogfile.txt. SSLKEYLOGFILE=$HOME/.mitmproxy/sslkeylogfile.txt mitmproxy -listen-port=1337 -rawtcp I have configured an Android device to use as a proxy the mitmproxy running on my Linux computer (opensuse Tumbleweed). I want to see in wireshark SSL/TLS packages from an Android phone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |