You cannot directly filter DTLS protocols while capturing. Show only the DTLS based traffic: dtls Capture Filter Type something in the client console and press enter, it should show up on the server console, and in Wireshark the DTLS packets should show this same data in an Application Data packet.Ī complete list of PROTO display filter fields can be found in the display filter reference.
$ openssl s_server -dtls -psk $PSK -cipher PSK-AES128-CBC-SHA -nocert -accept 23000Īs a client run this in another Linux console (Important to start capture before bringing up session below)Īs a server run this in a Linux console $ PSK=0102030405060708090a0b0c0d0e0f Start Wireshark, set DTLS preferences Pre-Shared Key to 0102030405060708090a0b0c0d0e0f Here's a working scenario on a Linux box,
Set RSA configuration to IP address:127.0.0.1, Port:4433, Protocol:data, Key File:/path/to/snakeoil-rsa.key Study the SSL page for details how to configure the RSA private key. This only works for RSA key exchange if the RSA keys can be provided. If Wireshark is compiled with SSL decryption support, there will be a new option in the preferences for DTLS. The DTLS dissector works with the OpenSSL v0.9.8b DTLS implementation. There is no well known UDP port for DTLS traffic. UDP: Typically DTLS uses UDP as its transport protocol.It's why this protocol is an adaptation of TLS 1.1 Protocol dependencies This protocol was created to do that which SSL can't : to create a secure protocol under UDP. DTLS is implemented by several projects including CyaSSL and the OpenSSL project. It provides the same security services (integrity, authentification and confidentiality) but under UDP protocol.
0 kommentar(er)
