Lines Matching refs:to
4 When debugging the QUIC stack it is extremely useful to have protocol traces
5 available. There are two approaches you can use to obtain this data:
10 Neither of these approaches is strictly superior to the other and both have pros
13 - In general, qlog is aimed at storing only information relevant to the
33 - Con: May leave out data assumed to be irrelevant
36 - Pro: No need to obtain a keylog
40 - Con: Need to obtain a keylog
49 - set the environment variable `QLOGDIR` to a directory where qlog log files
50 are to be written;
52 - set the environment variable `OSSL_QFILTER` to a filter specifying the events
53 you want to be written (set `OSSL_QFILTER='*'` for all events).
56 qlog files in the JSON-SEQ format to the specified directory. The files have the
63 can load at the click of a button, which enables you to see what kind of
73 Note that since qlog emphasises logging only data which is relevant to a QUIC
90 **Activating the decoder.** If you are using QUIC on a port not known to be
91 commonly used for QUIC, you may need to tell Wireshark to try and decode a flow
96 information without access to the encryption keys used for the connection
97 (though it is able to decrypt Initial packets).
99 In order to provide this information you need to provide Wireshark with a keylog
102 such a file is to enable a TLS or QUIC session to be decrypted for development
106 For the OpenSSL QUIC implementation, OpenSSL must be instructed to save a keylog
108 are using does not provide a way to enable this functionality, this requires
110 to enable this functionality directly.
112 If you are using OpenSSL QUIC to talk to another QUIC implementation, you also
113 may be able to obtain a keylog from that other implementation. (It does not
116 Once you have a keylog file you can configure Wireshark to use it.
117 There are two ways to do this:
120 Preferences and navigate to Protocols → TLS. Enter the path to the keylog file
122 appended to this log continuously if desired. Press OK and Wireshark should
123 now be able to decrypt any TLS or QUIC session described by the log file.
127 the packet capture file is opened. This avoids the need to have a centralised
130 to distribute a packet capture file publicly, for example for educational
