Re: relayd TLS handshake failure

2024-08-28 Thread David McMackins II
Another update on this issue: httpd is perfectly capable of negotiating a TLS handshake with my keypair. The error only happens in relayd. -- Regards, David E. McMackins II www.mcmackins.org On Thu, 2024-08-22 at 07:20 -0500, David McMackins II wrote: > Thanks for the tips. No mention of ecdsa

Re: relayd TLS handshake failure

2024-08-22 Thread David McMackins II
The only difference I notice between our configs is that your hostname.crt simlink goes to the leaf certificate and not the full chain. I've tried that as well to the same effect. This is leading me again to thinking it's to do with sparc64 architecture (or big endian generally) and not my configs.

Re: relayd TLS handshake failure

2024-08-22 Thread David McMackins II
Thanks for the tips. No mention of ecdsa in my acme-client.conf, and I've tried both the fullchain and leaf certs to the same effect. This morning I also tried a different gemini client just to make sure it wasn't a lagrange-specific issue, but alas. -- Regards, David E. McMackins II www.mcmack

Re: relayd TLS handshake failure

2024-08-22 Thread Stuart Henderson
On 2024/08/21 22:54, Omar Polo wrote: > On 21/08/24 14:49, Kirill A. Korinsky wrote: > > On Wed, 21 Aug 2024 14:32:34 +0200, > > David McMackins II wrote: > >> rsae_send_imsg: privenc poll timeout, keyop #0 > >> relay gemini, session 1 (1 active), 0, 192.168.1.1 -> :11965, TLS > >> handshake error

Re: relayd TLS handshake failure

2024-08-21 Thread Omar Polo
On 21/08/24 14:49, Kirill A. Korinsky wrote: > On Wed, 21 Aug 2024 14:32:34 +0200, > David McMackins II wrote: >> rsae_send_imsg: privenc poll timeout, keyop #0 >> relay gemini, session 1 (1 active), 0, 192.168.1.1 -> :11965, TLS >> handshake error: handshake failed: error:1402D438:SSL >> routines

Re: relayd TLS handshake failure

2024-08-21 Thread Sven Wolf
Hi David, I run vger 2.0.1 on amd64 as written by solene. my relayd.conf looks like yours cat /etc/relayd.conf log connection tcp protocol "gemini" { tls keypair } relay "gemini" { listen on port 1965 tls protocol "gemini" forward to 127.0.0.1 port 8965 } I also use the acme-cli

Re: relayd TLS handshake failure

2024-08-21 Thread Lucas Gabriel Vuotto
On Wed, Aug 21, 2024 at 07:32:34AM GMT, David McMackins II wrote: > Hello. > > I'm trying to set up a gemini server using vger and following the > instructions in its git repo: https://tildegit.org/solene/vger > > However, the TLS handshake with relayd is failing as follows: > > rsae_send_imsg:

Re: relayd TLS handshake failure

2024-08-21 Thread David McMackins II
Thanks. I should have mentioned I did already try adding the "tls tlsv1" directive in the gemini protocol section and it yielded the same result, so I removed it before opening this thread. -- Regards, David E. McMackins II www.mcmackins.org On Wed, 2024-08-21 at 14:49 +0200, Kirill A.Korinsky

Re: relayd TLS handshake failure

2024-08-21 Thread Kirill A . Korinsky
On Wed, 21 Aug 2024 14:32:34 +0200, David McMackins II wrote: > > rsae_send_imsg: privenc poll timeout, keyop #0 > relay gemini, session 1 (1 active), 0, 192.168.1.1 -> :11965, TLS > handshake error: handshake failed: error:1402D438:SSL > routines:ACCEPT_SW_CERT:tlsv1 alert internal error: Invali

relayd TLS handshake failure

2024-08-21 Thread David McMackins II
Hello. I'm trying to set up a gemini server using vger and following the instructions in its git repo: https://tildegit.org/solene/vger However, the TLS handshake with relayd is failing as follows: rsae_send_imsg: privenc poll timeout, keyop #0 relay gemini, session 1 (1 active), 0, 192.168.1.1