Hello Rob,

 RS> Having Synchronet/BinkIT listen/accept BINKP/TLS connections is a
 RS> piece of cake. Simply add the following to your ctrl/services.ini
 RS> file:

 RS> [BINKPS]
 RS> Enabled=true
 RS> Port=24555
 RS> Command=binkit.js
 RS> LogLevel=debug
 RS> Options=TLS

I have that setup now and binkit.js is listening also on port 24555 with the
TLS option.

A couple questions about sessions over TLS. Are session passwords required, and
is there anything else I need like a cert of some kind?

 RS> Now, having BinkIT support *outbound* BINKP/TLS connections will
 RS> require some (not a ton of) work (in JS); something I'll have to look
 RS> into. But if anyone wants to experiment, both vert.synchro.net and
 RS> cvs.synchro.net are answering BINKP/TLS connections on TCP port 24555
 RS> right now.

When that is ready I'll gladly test it out.

 RS> Also, I picked that TCP port number (24555) without a lot of debate,
 RS> so consider that a temporarly "assignment" until such time as BINKP
 RS> over TLS is more of a standard and an "official" port number is
 RS> assigned.

That should work fine I think.

I have Equinox BBS listening with standard binkp on port 24554 and secure
binkps on port 24554.

Equinox BBS
1:153/757.2
equinoxbbs.ddns.net

If anyone would like to try that feel free. Reports of success or failure are
welcome.

 Ttyl :-),
         Al

--- GoldED+/LNX 1.1.5-b20180707