Re: nc(1) fails the tls handshake when destination ends with a full stop

2021-05-30 Thread Florian Obser
On 2021-05-30 19:55 +02, Theo Buehler wrote: > On Sun, May 30, 2021 at 01:43:54PM -0400, Daniel Jakots wrote: >> On Sun, 30 May 2021 17:45:22 +0200, Theo Buehler >> wrote: >> >> > Unsure. If people really think this is useful and necessary, I can be >> > convinced. It's easy enough to do. And yo

Re: nc(1) fails the tls handshake when destination ends with a full stop

2021-05-30 Thread Daniel Jakots
On Sun, 30 May 2021 19:55:42 +0200, Theo Buehler wrote: > On Sun, May 30, 2021 at 01:43:54PM -0400, Daniel Jakots wrote: > > On Sun, 30 May 2021 17:45:22 +0200, Theo Buehler > > wrote: > > > > > Unsure. If people really think this is useful and necessary, I > > > can be convinced. It's easy e

Re: nc(1) fails the tls handshake when destination ends with a full stop

2021-05-30 Thread Theo Buehler
On Sun, May 30, 2021 at 01:43:54PM -0400, Daniel Jakots wrote: > On Sun, 30 May 2021 17:45:22 +0200, Theo Buehler > wrote: > > > Unsure. If people really think this is useful and necessary, I can be > > convinced. It's easy enough to do. And you're right, curl strips the > > trailing dot after re

Re: nc(1) fails the tls handshake when destination ends with a full stop

2021-05-30 Thread Daniel Jakots
On Sun, 30 May 2021 17:45:22 +0200, Theo Buehler wrote: > Unsure. If people really think this is useful and necessary, I can be > convinced. It's easy enough to do. And you're right, curl strips the > trailing dot after resolving a host name for SNI and HTTP host header. Given the current error

Re: nc(1) fails the tls handshake when destination ends with a full stop

2021-05-30 Thread Theo Buehler
On Sun, May 30, 2021 at 02:31:55PM -, Stuart Henderson wrote: > On 2021-05-30, Theo Buehler wrote: > > On Sat, May 29, 2021 at 10:37:18PM -0400, Daniel Jakots wrote: > >> Hi, > >> > >> $ nc -zvc openbsd.org 443 # works as expected > >> Connection to openbsd.org (129.128.5.194) 443 port [tcp/h

Re: nc(1) fails the tls handshake when destination ends with a full stop

2021-05-30 Thread Stuart Henderson
On 2021-05-30, Theo Buehler wrote: > On Sat, May 29, 2021 at 10:37:18PM -0400, Daniel Jakots wrote: >> Hi, >> >> $ nc -zvc openbsd.org 443 # works as expected >> Connection to openbsd.org (129.128.5.194) 443 port [tcp/https] succeeded! >> TLS handshake negotiated TLSv1.3/AEAD-AES256-GCM-SHA384 wi

Re: nc(1) fails the tls handshake when destination ends with a full stop

2021-05-30 Thread Theo Buehler
On Sat, May 29, 2021 at 10:37:18PM -0400, Daniel Jakots wrote: > Hi, > > $ nc -zvc openbsd.org 443 # works as expected > Connection to openbsd.org (129.128.5.194) 443 port [tcp/https] succeeded! > TLS handshake negotiated TLSv1.3/AEAD-AES256-GCM-SHA384 with host openbsd.org > [...] > > $ nc -zvc

nc(1) fails the tls handshake when destination ends with a full stop

2021-05-29 Thread Daniel Jakots
Hi, $ nc -zvc openbsd.org 443 # works as expected Connection to openbsd.org (129.128.5.194) 443 port [tcp/https] succeeded! TLS handshake negotiated TLSv1.3/AEAD-AES256-GCM-SHA384 with host openbsd.org [...] $ nc -zvc openbsd.org. 443 # fails Connection to openbsd.org. (129.128.5.194) 443 port [t