Hi Wilfred.

13 Dec 19 21:37:30, you wrote to me:

 WV>>> I had to do this slightly different:

 WV>>> /etc/stunnel # cat binkps.conf
 WV>>> cert=/etc/letsencrypt/live/vlzn.nl/fullchain.pem
 WV>>> key=/etc/letsencrypt/live/vlzn.nl/privkey.pem
 WV>>> connect=24554

 TK>> Ok. I can live with that. :)

 WV> Those are the files letsencrypt generates by default. Don't you need to
specify your
 WV> (private) key?

Yes. That "web.pem" of mine contains both. Your way is better, I changed to
that. Thanks!

 WV>>> But it seems to work. Can anyone test my node? TLS/SSL connects to my
 WV>>> binkd for node 2:280/464 should go to fido.vlzn.nl:24553

 TK>> === Cut ===
 TK>>   13 Dec 22:15:54 [14318] Substituted * to fido.vlzn.nl. for
 TK>> 2:280/464@fidonet by nodelist + 13 Dec 22:15:54 [14318] call to
 TK>> 2:280/464@fidonet + 13 Dec 22:15:54 [14318] External command 'openssl
 TK>> s_client -quiet -alpn binkp -connect fido.vlzn.nl:24553' started, pid
14319
 TK>>   13 Dec 22:15:54 [14318] connected
 TK>> + 13 Dec 22:15:54 [14318] outgoing session with fido.vlzn.nl:binkp

 WV> It works! :-)

:-)

Another stunnel is now up for 2:221/360: rbb.fidonet.fi, port 24567: stunnel in
linux, binkd in OS/2. ;)

 WV> I'm only a bit surprised it came in on IPv4 not like your regular
 WV> connections on IPv6!?

I wonder why openssl in linux prefers ipv4..?

'Tommi

---