<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — Creating a NSS Key Log File]]></title>
		<link>https://www.wolfssl.com/forums/topic1580-creating-a-nss-key-log-file.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic1580.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Creating a NSS Key Log File.]]></description>
		<lastBuildDate>Wed, 24 Mar 2021 23:33:39 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Creating a NSS Key Log File]]></title>
			<link>https://www.wolfssl.com/forums/post5925.html#p5925</link>
			<description><![CDATA[<p>Hi All,</p><p>I have posted an example for using our TLS v1.3 secret logging here:<br /><a href="https://github.com/wolfSSL/wolfssl-examples/pull/251">https://github.com/wolfSSL/wolfssl-examples/pull/251</a></p><p>Thanks,<br />David Garske, wolfSSL</p>]]></description>
			<author><![CDATA[null@example.com (dgarske)]]></author>
			<pubDate>Wed, 24 Mar 2021 23:33:39 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post5925.html#p5925</guid>
		</item>
		<item>
			<title><![CDATA[Re: Creating a NSS Key Log File]]></title>
			<link>https://www.wolfssl.com/forums/post5921.html#p5921</link>
			<description><![CDATA[<p>Hi cxenof03,</p><p>That is correct. For TLS v1.3 you can use HAVE_SECRET_CALLBACK and wolfSSL_set_tls13_secret_cb to setup a callback for printing the secrets for use with Wireshark.</p><p>The WOLFSSL_STATIC_EPHEMERAL feature does allow you to use a fixed ephemeral key for testing, which can be loaded into Wireshark. The WOLFSSL_STATIC_EPHEMERAL is meant to be used with the WOLFSSL sniffer (--enable-sniffer) and sslSniffer/sslSnifferTest, which allows decryption of the TLS traffic.</p><p>If you&#039;d like some additional documentation on this please email us directly using support@wolfssl.com.</p><p>Thanks,<br />David Garske, wolfSSL</p>]]></description>
			<author><![CDATA[null@example.com (dgarske)]]></author>
			<pubDate>Wed, 24 Mar 2021 18:14:23 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post5921.html#p5921</guid>
		</item>
		<item>
			<title><![CDATA[Re: Creating a NSS Key Log File]]></title>
			<link>https://www.wolfssl.com/forums/post5916.html#p5916</link>
			<description><![CDATA[<p>@dgarske <br />Does that support TLS 1.3 though ? I have enabled the flags and also use <em>WOLFSSL_STATIC_EPHEMERAL</em> in order to capture my TLS 1.3 packets with the sniffer etc.<br />If no, how can I decrypt the traffic exchanged from a local server-client ( from the examples ) and watch it on wireshark or any similar traffic analyzer ?</p><p>Thank you</p>]]></description>
			<author><![CDATA[null@example.com (cxenof03)]]></author>
			<pubDate>Wed, 24 Mar 2021 02:29:48 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post5916.html#p5916</guid>
		</item>
		<item>
			<title><![CDATA[Re: Creating a NSS Key Log File]]></title>
			<link>https://www.wolfssl.com/forums/post5369.html#p5369</link>
			<description><![CDATA[<p>Hi he1n,</p><p>Yes. See `WOLFSSL_SSLKEYLOGFILE` define to output master secret used by Wireshark logging to file. Defaults to sslkeylog.log, but can be overridden using `WOLFSSL_SSLKEYLOGFILE_OUTPUT`.</p><p>1. Build wolfSSL using:<br />./configure CFLAGS=&quot;-DSHOW_SECRETS -DWOLFSSL_SSLKEYLOGFILE&quot;</p><p>2. By default it outputs to a file named &quot;sslkeylog.log&quot; using this Wireshark Pre-Master-Secret Format:<br />CLIENT_RANDOM &lt;clientrandom&gt; &lt;mastersecret&gt;</p><p>3. You can tell Wireshark where to find the key file via Edit→Preferences→Protocols→SSL→(Pre)-Master-Secret log filename.</p><p>Key logging feature was added in PR 1873 (<a href="https://github.com/wolfSSL/wolfssl/pull/1873">https://github.com/wolfSSL/wolfssl/pull/1873</a>)<br />Commit: <a href="https://github.com/wolfSSL/wolfssl/pull/1873/commits/23a0f3cfa17f5437b38e3eca1eb1eddd532b587b">https://github.com/wolfSSL/wolfssl/pull … dd532b587b</a></p><p>You will get a compiler warning for this feature because it should never be used in production. Here is the PR with those details:<br /><a href="https://github.com/wolfSSL/wolfssl/pull/2053">https://github.com/wolfSSL/wolfssl/pull/2053</a></p><p>The #warning can be ignored as error using ./configure CFLAGS=&quot;-W#warnings&quot;.</p><p>Thanks,<br />David Garske, wolfSSL</p>]]></description>
			<author><![CDATA[null@example.com (dgarske)]]></author>
			<pubDate>Thu, 23 Jul 2020 17:26:17 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post5369.html#p5369</guid>
		</item>
		<item>
			<title><![CDATA[Creating a NSS Key Log File]]></title>
			<link>https://www.wolfssl.com/forums/post5368.html#p5368</link>
			<description><![CDATA[<p>Hi,</p><p>I am using WolfSSL and I want to create a key log file like specified here: <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format">https://developer.mozilla.org/en-US/doc … Log_Format</a>. On OpenSSL this is fairly easy, as I can use SSL_CTX_set_keylog_callback to set a callback function, which receives all keys that are being created. Is there a similar easy way to archieve this in WolfSSL? </p><p>Best regards<br />he1n</p>]]></description>
			<author><![CDATA[null@example.com (he1n)]]></author>
			<pubDate>Thu, 23 Jul 2020 07:36:39 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post5368.html#p5368</guid>
		</item>
	</channel>
</rss>
