Re: Ialternaernaernative transports
  By: Alan Ianson to Rob Swindell on Mon Dec 09 2019 04:42 pm

 > 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?

A session password would be required for "secure" sessions, the same as when
not using TLS. And you should already have a cert file: ctrl/ssl.cert. It's a
self-signed certificate by default, or you can get one from LetsEncrypt using
the Synchronet letSyncrypt module.


                                            digital man

Synchronet/BBS Terminology Definition #53:
PETSCII = PET Standard Code of Information Interchange (a.k.a. CBM ASCII)
Norco, CA WX: 63.4øF, 52.0% humidity, 3 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.10-Linux