kernel-tls-handshake.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "kernel-tls-handshake@lists.linux.dev"
	<kernel-tls-handshake@lists.linux.dev>
Subject: Re: Test results from v4
Date: Fri, 17 Feb 2023 12:36:12 +0100	[thread overview]
Message-ID: <0aafe14a-5153-c02c-85d3-9568bc7e3bd0@suse.de> (raw)
In-Reply-To: <66F7EBA7-AA44-4FAD-B7E2-20FBEBC74C2A@oracle.com>

On 2/16/23 18:17, Chuck Lever III wrote:
> 
>> On Feb 16, 2023, at 11:57 AM, Hannes Reinecke <hare@suse.de> wrote:
>>
>>
>> I've got some patches queued up to enable PSK for v4 (both client and server side), how should I post them? Here on the list or on the general linux-block / linux-nvme list?
> 
> Start here, let's see what you got.
> 
Done.

Handshake looks good, _except_ that the server side refuses to fetch new 
packets until client side closes the connection due to a timeout:

tlshd[11024]: (11024) gnutls(5): REC[0x209cc40]: Preparing Packet 
Handshake(22) with length: 559 and min pad: 0
tlshd[11024]: (11024) gnutls(9): ENC[0x209cc40]: cipher: NULL, MAC: 
MAC-NULL, Epoch: 0
tlshd[11024]: (11024) gnutls(5): REC[0x209cc40]: Sent Packet[1] 
Handshake(22) in epoch 0 and length: 564
tlshd[11024]: (11024) gnutls: The operation timed out (-319)
tlshd[11024]: (11024) Handshake with c472.arch.suse.de (10.161.60.216) 
failed
tlshd[11023]: (11023) gnutls(5): REC[0x209cbc0]: SSL 3.1 Handshake 
packet received. Epoch 0, length: 559

Any idea what could be causing it?
(And I checked, the ClientHello packet really is on the wire, so it's a 
server-side thingie).
I'm pretty sure the server side doesn't set any callbacks to the socket 
(yet), so I'm a bit at a loss what could be the reason here.

Thanks for any pointers.

Cheers,

Hannes


  reply	other threads:[~2023-02-17 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 15:58 Test results from v4 Hannes Reinecke
2023-02-16 16:03 ` Chuck Lever III
2023-02-16 16:10   ` Chuck Lever III
2023-02-16 16:57   ` Hannes Reinecke
2023-02-16 17:17     ` Chuck Lever III
2023-02-17 11:36       ` Hannes Reinecke [this message]
2023-02-17 11:56         ` Chuck Lever III
2023-02-22 16:22           ` Chuck Lever III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0aafe14a-5153-c02c-85d3-9568bc7e3bd0@suse.de \
    --to=hare@suse.de \
    --cc=chuck.lever@oracle.com \
    --cc=kernel-tls-handshake@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).