dev.linux.lists.kernel-tls-handshake archive

416 archived articles, newest first (page 3 of 5). Latest articles →

Re: [PATCH net-next v10 3/7] tls: Re-present partially-consumed records in tls_sw_read_sock()
Tue, 12 May 2026 18:24:40 -0700
Jakub Kicinski <[email protected]> • #1813
Re: [PATCH net-next v10 3/7] tls: Re-present partially-consumed records in tls_sw_read_sock()
Tue, 12 May 2026 21:11:39 -0400
"Chuck Lever" <[email protected]> • #1812
Re: [PATCH net-next v10 3/7] tls: Re-present partially-consumed records in tls_sw_read_sock()
Tue, 12 May 2026 17:17:15 -0700
Jakub Kicinski <[email protected]> • #1811
Re: [PATCH net-next v10 3/7] tls: Re-present partially-consumed records in tls_sw_read_sock()
Tue, 12 May 2026 14:52:59 +0200
Sabrina Dubroca <[email protected]> • #1810
[PATCH net-next v10 7/7] tls: Preserve sk_err across recvmsg() when data has been copied
Mon, 11 May 2026 19:25:58 -0400
Chuck Lever <[email protected]> • #1809
[PATCH net-next v10 6/7] tls: Flush backlog before waiting for a new record
Mon, 11 May 2026 19:25:57 -0400
Chuck Lever <[email protected]> • #1808
[PATCH net-next v10 5/7] tls: Suppress spurious saved_data_ready on all receive paths
Mon, 11 May 2026 19:25:56 -0400
Chuck Lever <[email protected]> • #1807
[PATCH net-next v10 4/7] tls: Factor tls_strp_msg_consume() from tls_strp_msg_done()
Mon, 11 May 2026 19:25:55 -0400
Chuck Lever <[email protected]> • #1806
[PATCH net-next v10 3/7] tls: Re-present partially-consumed records in tls_sw_read_sock()
Mon, 11 May 2026 19:25:54 -0400
Chuck Lever <[email protected]> • #1805
[PATCH net-next v10 2/7] tls: Avoid evaluating freed skb in tls_sw_read_sock() loop
Mon, 11 May 2026 19:25:53 -0400
Chuck Lever <[email protected]> • #1804
[PATCH net-next v10 1/7] tls: Move decrypt-failure abort into tls_rx_one_record()
Mon, 11 May 2026 19:25:52 -0400
Chuck Lever <[email protected]> • #1803
[PATCH net-next v10 0/7] tls: receive-path fixes and clean-ups
Mon, 11 May 2026 19:25:51 -0400
Chuck Lever <[email protected]> • #1802
[ANNOUNCE] ktls-utils 1.3.1
Mon, 11 May 2026 15:35:25 -0400
Chuck Lever <[email protected]> • #1801
Fwd: [oracle/ktls-utils] tlshd/handshake: handle the UNKNOWN_PSK_IDENTITY alert (PR #149)
Mon, 11 May 2026 07:17:01 -0400
"Chuck Lever" <[email protected]> • #1800
[ANNOUNCE] ktls 1.4.0
Sat, 9 May 2026 13:04:41 -0400
Chuck Lever <[email protected]> • #1799
Re: Breakage in ktls-utils with nfs keyring?
Tue, 5 May 2026 11:32:33 +0300
Sagi Grimberg <[email protected]> • #1798
Re: Breakage in ktls-utils with nfs keyring?
Tue, 05 May 2026 10:15:48 +0200
"Chuck Lever" <[email protected]> • #1797
Re: [PATCH net-next v9 0/5] TLS read_sock performance scalability
Mon, 04 May 2026 17:59:12 +0200
"Chuck Lever" <[email protected]> • #1796
Re: [PATCH net-next v9 0/5] TLS read_sock performance scalability
Mon, 4 May 2026 15:33:29 +0200
Sabrina Dubroca <[email protected]> • #1795
Re: Breakage in ktls-utils with nfs keyring?
Mon, 4 May 2026 10:21:51 +0200
Hannes Reinecke <[email protected]> • #1794
Re: Breakage in ktls-utils with nfs keyring?
Mon, 4 May 2026 11:02:17 +0300
Sagi Grimberg <[email protected]> • #1793
Fwd: [oracle/ktls-utils] Enable and prioritize post quantum EC groups (PR #147)
Mon, 04 May 2026 09:06:27 +0200
"Chuck Lever" <[email protected]> • #1792
Re: Breakage in ktls-utils with nfs keyring?
Mon, 04 May 2026 08:44:01 +0200
"Chuck Lever" <[email protected]> • #1791
Re: Breakage in ktls-utils with nfs keyring?
Sun, 3 May 2026 23:37:39 +0300
Sagi Grimberg <[email protected]> • #1790
Re: [PATCH net-next v9 0/5] TLS read_sock performance scalability
Sun, 3 May 2026 21:34:01 +0200
Chuck Lever <[email protected]> • #1789
Re: Breakage in ktls-utils with nfs keyring?
Sun, 03 May 2026 21:11:27 +0200
"Chuck Lever" <[email protected]> • #1788
Re: Breakage in ktls-utils with nfs keyring?
Sun, 3 May 2026 10:48:54 +0300
Sagi Grimberg <[email protected]> • #1787
Re: [PATCH] tlshd: fix keyring cert retrieval
Sun, 3 May 2026 10:30:57 +0300
Sagi Grimberg <[email protected]> • #1786
Re: [PATCH net-next v9 1/5] tls: Abort the connection on decrypt failure
Sat, 2 May 2026 18:20:48 -0700
Jakub Kicinski <[email protected]> • #1785
Re: [PATCH net-next v9 4/5] tls: Suppress spurious saved_data_ready on all receive paths
Sat, 2 May 2026 18:19:21 -0700
Jakub Kicinski <[email protected]> • #1784
Re: [PATCH net-next v9 3/5] tls: Factor tls_strp_msg_release() from tls_strp_msg_done()
Sat, 2 May 2026 18:09:01 -0700
Jakub Kicinski <[email protected]> • #1783
Re: [PATCH net-next v9 2/5] tls: Fix dangling skb pointer in tls_sw_read_sock()
Sat, 2 May 2026 18:05:15 -0700
Jakub Kicinski <[email protected]> • #1782
Re: [PATCH net-next v9 0/5] TLS read_sock performance scalability
Sat, 2 May 2026 18:04:15 -0700
Jakub Kicinski <[email protected]> • #1781
Re: Breakage in ktls-utils with nfs keyring?
Fri, 01 May 2026 23:08:15 -0400
"Chuck Lever" <[email protected]> • #1780
Re: Breakage in ktls-utils with nfs keyring?
Fri, 1 May 2026 16:19:25 -0400
Scott Mayhew <[email protected]> • #1779
[PATCH] tlshd: fix keyring cert retrieval
Fri, 1 May 2026 15:58:56 -0400
Scott Mayhew <[email protected]> • #1778
Re: Breakage in ktls-utils with nfs keyring?
Thu, 30 Apr 2026 09:38:15 -0400
"Chuck Lever" <[email protected]> • #1777
Re: [PATCH net-next v9 0/5] TLS read_sock performance scalability
Wed, 29 Apr 2026 19:15:41 -0400
"Chuck Lever" <[email protected]> • #1776
Re: [PATCH net-next v9 0/5] TLS read_sock performance scalability
Wed, 29 Apr 2026 16:13:38 -0700
Jakub Kicinski <[email protected]> • #1775
[PATCH net-next v9 5/5] tls: Flush backlog before waiting for a new record
Wed, 29 Apr 2026 17:48:12 -0400
Chuck Lever <[email protected]> • #1774
[PATCH net-next v9 4/5] tls: Suppress spurious saved_data_ready on all receive paths
Wed, 29 Apr 2026 17:48:11 -0400
Chuck Lever <[email protected]> • #1773
[PATCH net-next v9 3/5] tls: Factor tls_strp_msg_release() from tls_strp_msg_done()
Wed, 29 Apr 2026 17:48:10 -0400
Chuck Lever <[email protected]> • #1772
[PATCH net-next v9 2/5] tls: Fix dangling skb pointer in tls_sw_read_sock()
Wed, 29 Apr 2026 17:48:09 -0400
Chuck Lever <[email protected]> • #1771
[PATCH net-next v9 1/5] tls: Abort the connection on decrypt failure
Wed, 29 Apr 2026 17:48:08 -0400
Chuck Lever <[email protected]> • #1770
[PATCH net-next v9 0/5] TLS read_sock performance scalability
Wed, 29 Apr 2026 17:48:07 -0400
Chuck Lever <[email protected]> • #1769
[PATCH net-next v8 5/5] tls: Flush backlog before waiting for a new record
Tue, 28 Apr 2026 09:30:50 -0400
Chuck Lever <[email protected]> • #1768
[PATCH net-next v8 4/5] tls: Suppress spurious saved_data_ready on all receive paths
Tue, 28 Apr 2026 09:30:49 -0400
Chuck Lever <[email protected]> • #1767
[PATCH net-next v8 3/5] tls: Factor tls_strp_msg_release() from tls_strp_msg_done()
Tue, 28 Apr 2026 09:30:48 -0400
Chuck Lever <[email protected]> • #1766
[PATCH net-next v8 2/5] tls: Fix dangling skb pointer in tls_sw_read_sock()
Tue, 28 Apr 2026 09:30:47 -0400
Chuck Lever <[email protected]> • #1765
[PATCH net-next v8 1/5] tls: Abort the connection on decrypt failure
Tue, 28 Apr 2026 09:30:46 -0400
Chuck Lever <[email protected]> • #1764
[PATCH net-next v8 0/5] TLS read_sock performance scalability
Tue, 28 Apr 2026 09:30:45 -0400
Chuck Lever <[email protected]> • #1763
Re: [PATCH net-next v7 0/5] TLS read_sock performance scalability
Sun, 26 Apr 2026 16:55:51 -0700
Jakub Kicinski <[email protected]> • #1762
Re: [PATCH net-next v7 0/5] TLS read_sock performance scalability
Sat, 25 Apr 2026 16:15:41 -0400
"Chuck Lever" <[email protected]> • #1761
Re: [PATCH net-next v7 0/5] TLS read_sock performance scalability
Wed, 22 Apr 2026 19:08:15 -0700
Jakub Kicinski <[email protected]> • #1760
Re: [PATCH net-next v7 0/5] TLS read_sock performance scalability
Wed, 22 Apr 2026 12:41:43 -0400
"Chuck Lever" <[email protected]> • #1759
[PATCH v2] tlshd: Add runtime check for ML-DSA support in gnutls
Wed, 15 Apr 2026 14:13:59 -0400
Chuck Lever <[email protected]> • #1758
[PATCH] tlshd: Add runtime check for ML-DSA support in gnutls
Wed, 15 Apr 2026 13:18:17 -0400
Chuck Lever <[email protected]> • #1757
Re: [PATCH net-next v7 4/5] tls: Suppress spurious saved_data_ready on all receive paths
Mon, 30 Mar 2026 22:06:01 -0400
"Chuck Lever" <[email protected]> • #1756
Re: [PATCH net-next v7 4/5] tls: Suppress spurious saved_data_ready on all receive paths
Mon, 30 Mar 2026 16:43:44 +0200
Sabrina Dubroca <[email protected]> • #1755
Re: [PATCH net-next v7 3/5] tls: Factor tls_strp_msg_release() from tls_strp_msg_done()
Mon, 30 Mar 2026 14:21:16 +0200
Sabrina Dubroca <[email protected]> • #1754
Re: [PATCH net-next v7 2/5] tls: Fix dangling skb pointer in tls_sw_read_sock()
Mon, 30 Mar 2026 14:17:07 +0200
Sabrina Dubroca <[email protected]> • #1753
[PATCH net-next v7 5/5] tls: Flush backlog before waiting for a new record
Sat, 28 Mar 2026 11:17:12 -0400
Chuck Lever <[email protected]> • #1752
[PATCH net-next v7 4/5] tls: Suppress spurious saved_data_ready on all receive paths
Sat, 28 Mar 2026 11:17:11 -0400
Chuck Lever <[email protected]> • #1751
[PATCH net-next v7 3/5] tls: Factor tls_strp_msg_release() from tls_strp_msg_done()
Sat, 28 Mar 2026 11:17:10 -0400
Chuck Lever <[email protected]> • #1750
[PATCH net-next v7 2/5] tls: Fix dangling skb pointer in tls_sw_read_sock()
Sat, 28 Mar 2026 11:17:09 -0400
Chuck Lever <[email protected]> • #1749
[PATCH net-next v7 1/5] tls: Abort the connection on decrypt failure
Sat, 28 Mar 2026 11:17:08 -0400
Chuck Lever <[email protected]> • #1748
[PATCH net-next v7 0/5] TLS read_sock performance scalability
Sat, 28 Mar 2026 11:17:07 -0400
Chuck Lever <[email protected]> • #1747
Re: [PATCH net-next v6 0/6] TLS read_sock performance scalability
Fri, 27 Mar 2026 17:26:07 -0700
Jakub Kicinski <[email protected]> • #1746
Re: [PATCH net-next v6 0/6] TLS read_sock performance scalability
Fri, 27 Mar 2026 09:35:09 -0400
"Chuck Lever" <[email protected]> • #1745
Re: [PATCH net-next v11 06/15] quic: add stream management
Thu, 26 Mar 2026 18:00:01 -0700
Jakub Kicinski <[email protected]> • #1744
Re: [PATCH net-next v6 0/6] TLS read_sock performance scalability
Thu, 26 Mar 2026 17:54:30 -0700
Jakub Kicinski <[email protected]> • #1743
Re: [PATCH net-next v6 0/6] TLS read_sock performance scalability
Thu, 26 Mar 2026 22:34:42 +0000
[email protected] • #1742
Re: [PATCH net-next v11 06/15] quic: add stream management
Thu, 26 Mar 2026 17:48:51 -0400
Xin Long <[email protected]> • #1741
Re: [PATCH net-next v11 06/15] quic: add stream management
Thu, 26 Mar 2026 13:07:40 -0700
Jakub Kicinski <[email protected]> • #1740
Re: [PATCH net-next v11 12/15] quic: add crypto packet encryption and decryption
Thu, 26 Mar 2026 11:10:25 -0400
Xin Long <[email protected]> • #1739
Re: [PATCH net-next v11 06/15] quic: add stream management
Thu, 26 Mar 2026 11:06:26 -0400
Xin Long <[email protected]> • #1738
[PATCH net-next v6 6/6] tls: Flush backlog before waiting for a new record
Thu, 26 Mar 2026 09:50:51 -0400
Chuck Lever <[email protected]> • #1737
[PATCH net-next v6 5/6] tls: Suppress spurious saved_data_ready on all receive paths
Thu, 26 Mar 2026 09:50:50 -0400
Chuck Lever <[email protected]> • #1736
[PATCH net-next v6 4/6] tls: Factor tls_strp_msg_release() from tls_strp_msg_done()
Thu, 26 Mar 2026 09:50:49 -0400
Chuck Lever <[email protected]> • #1735
[PATCH net-next v6 3/6] tls: Fix dangling skb pointer in tls_sw_read_sock()
Thu, 26 Mar 2026 09:50:48 -0400
Chuck Lever <[email protected]> • #1734
[PATCH net-next v6 2/6] tls: Abort the connection on decrypt failure
Thu, 26 Mar 2026 09:50:47 -0400
Chuck Lever <[email protected]> • #1733
[PATCH net-next v6 1/6] tls: Purge async_hold in tls_decrypt_async_wait()
Thu, 26 Mar 2026 09:50:46 -0400
Chuck Lever <[email protected]> • #1732
[PATCH net-next v6 0/6] TLS read_sock performance scalability
Thu, 26 Mar 2026 09:50:45 -0400
Chuck Lever <[email protected]> • #1731
Re: [PATCH net-next v5 1/6] tls: Purge async_hold in tls_decrypt_async_wait()
Thu, 26 Mar 2026 11:32:18 +0100
Hannes Reinecke <[email protected]> • #1730
Re: [PATCH net-next v5 0/6] TLS read_sock performance scalability
Thu, 26 Mar 2026 09:10:05 +0000
[email protected] • #1729
Re: [PATCH net-next v5 6/6] tls: Flush backlog before waiting for a new record
Thu, 26 Mar 2026 09:59:13 +0100
Sabrina Dubroca <[email protected]> • #1728
[PATCH net-next v11 15/15] quic: add packet parser base
Tue, 24 Mar 2026 23:47:20 -0400
Xin Long <[email protected]> • #1727
[PATCH net-next v11 14/15] quic: add packet builder base
Tue, 24 Mar 2026 23:47:19 -0400
Xin Long <[email protected]> • #1726
[PATCH net-next v11 13/15] quic: add timer management
Tue, 24 Mar 2026 23:47:18 -0400
Xin Long <[email protected]> • #1725
[PATCH net-next v11 12/15] quic: add crypto packet encryption and decryption
Tue, 24 Mar 2026 23:47:17 -0400
Xin Long <[email protected]> • #1724
[PATCH net-next v11 11/15] quic: add crypto key derivation and installation
Tue, 24 Mar 2026 23:47:16 -0400
Xin Long <[email protected]> • #1723
[PATCH net-next v11 10/15] quic: add packet number space
Tue, 24 Mar 2026 23:47:15 -0400
Xin Long <[email protected]> • #1722
[PATCH net-next v11 09/15] quic: add congestion control
Tue, 24 Mar 2026 23:47:14 -0400
Xin Long <[email protected]> • #1721
[PATCH net-next v11 08/15] quic: add path management
Tue, 24 Mar 2026 23:47:13 -0400
Xin Long <[email protected]> • #1720
[PATCH net-next v11 07/15] quic: add connection id management
Tue, 24 Mar 2026 23:47:12 -0400
Xin Long <[email protected]> • #1719
[PATCH net-next v11 06/15] quic: add stream management
Tue, 24 Mar 2026 23:47:11 -0400
Xin Long <[email protected]> • #1718
[PATCH net-next v11 05/15] quic: provide quic.h header files for kernel and userspace
Tue, 24 Mar 2026 23:47:10 -0400
Xin Long <[email protected]> • #1717
[PATCH net-next v11 04/15] quic: provide family ops for address and protocol
Tue, 24 Mar 2026 23:47:09 -0400
Xin Long <[email protected]> • #1716
[PATCH net-next v11 03/15] quic: provide common utilities and data structures
Tue, 24 Mar 2026 23:47:08 -0400
Xin Long <[email protected]> • #1715
[PATCH net-next v11 02/15] net: build socket infrastructure for QUIC protocol
Tue, 24 Mar 2026 23:47:07 -0400
Xin Long <[email protected]> • #1714
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.