Wireless Transport Layer Service is an optional protocol which provides bearer-level security, in a way similar to TLS for end-to-end security. If the wireless bearer already provides over-the-air security (to make eavesdropping more difficult by encrypting the data sent over the air), then WTLS is not required. This is the case for GSM CSD and GSM GPRS for example.
It is a common misconception that WTLS provides end-to-end security in WAP. This is not true. This "myth" probably originated in the way a secure HTTP connection is initiated by writing "https://" instead of "http://" in your web browser. The analogy was thougt to be the presence of WTLS. This issue is that between the WSP client device and the WAP Gateway, the URL is sent in cleartext and the HTTP response is sent back in cleartext to the device.
XXX - add a brief description of WTLS history
XXX - Add example traffic here (as plain text or Wireshark screenshot).
The WTLS dissector is fully functional. Decryption however is not provided yet.
There are no preferences for WTLS in Wireshark.
XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.
A complete list of WTLS display filter fields can be found in the display filter reference
Show only the WTLS based traffic:
You cannot directly filter WTLS traffic while capturing. However, if you know the transport protocol (bearer) used (see above), you can filter on that one.
Imported from https://wiki.wireshark.org/Wireless_Transport_Layer_Security on 2020-08-11 23:27:35 UTC