Re: RE: Iand alternaernative transports
  By: Alan Ianson to Oli on Mon Nov 18 2019 02:09 pm

 > by TLS proxy so I'd need to be educated about these things before any
 > meaningful tests could be done.. :)
 >
 >  Ol> If you want to test it (TLS or Tor) we can discuss it in FSX_CRY and/or
 >  Ol> BINKD. Just start a thread there, I read both areas.
 >
 > I don't mind testing either, but as I say I don't know either so you
 > would need to bring me up to speed.
 >
 > I'd be most interested in something that can be used with the binkp
 > protocol (if that's desirable) in all it's various uses with binkd,
 > BinkIT and other mailers that would/could use it.

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

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

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

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

                                            digital man

Synchronet "Real Fact" #3:
Synchronet version 2 was written in C and 8086 assembly programming languages.
Norco, CA WX: 63.4øF, 61.0% humidity, 8 mph ENE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.10-Linux