Subj : Ialternaernaernative transports
To   : Tommi Koivula
From : Oli
Date : Fri Dec 13 2019 10:03 pm

 TK>> Would you explain this "external command"? How to run it from
 TK>> binkd?

 TK> Never mind, I got it:

 TK> === Cut ===
 TK> node 2:221/6 -pipe "openssl s_client -quiet -alpn binkp -connect
 TK> news.fidonet.fi:24567" *
 TK> === Cut ===

alternatice command is

node 2:221/6 -pipe "ncat --ssl-alpn binkp *H *I" news.fidonet.fi:24567

The alpn stuff is only needed if the server demands it (e.g when running 
webserver, xmpp server, binkp on port 443). I use "ncat --ssl-alpn binkp H* 
I*", because "ncat --ssl H* I*" invokes ncat with the port number "I*" instead 
of the real port number. I guess this is a bug in binkd. Some problem with 
parsing the -pipe parameter?

I wonder, if we should directly jump to QUIC instead of implementing TLS over 
TCP?

 
* Origin: kakistocracy (2:280/464.47)

.