Date: Tue, 3 Mar 2020 00:02:23 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: John Baldwin <jhb@FreeBSD.org>, Rick Macklem <rmacklem@FreeBSD.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-projects@freebsd.org" <svn-src-projects@freebsd.org> Subject: Re: svn commit: r358053 - projects/nfs-over-tls/sys/fs/nfsclient Message-ID: <YTBPR01MB33747BF98BDDFC546AC17648DDE70@YTBPR01MB3374.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <de3e5a30-c36a-916d-2de1-1ee4154d2782@FreeBSD.org> References: <202002172110.01HLAXZY003012@repo.freebsd.org> <fccc4f14-6b8a-7ab2-6614-52da1561946b@FreeBSD.org> <YTBPR01MB33742D4B8CB9DB7107564927DDE90@YTBPR01MB3374.CANPRD01.PROD.OUTLOOK.COM>, <de3e5a30-c36a-916d-2de1-1ee4154d2782@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: [stuff snipped] >I started testing my KTLS RX software branch Friday btw (panicked right away >of course, but it's hopefully not too far away). For now I'm only focused on >TLS 1.0-1.2, but will get to 1.3 eventually. I suspect for 1.3 that early data >will still be handled in userland and just as for KTLS TX, KTLS RX will only >be used with the second set of keys. Just fyi, when I switch the client side daemon to use TLS1.2 instead of TLS1.3, those two records (238 bytes each) that showed up in the socket receive queue do not show up. (ie. They are TLS1.3 specific, so we won't need to worry about them for now.) Have fun with it, rick -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTBPR01MB33747BF98BDDFC546AC17648DDE70>