Subj : Re^2:  Re^4:  Directly include binary data in messages
To   : James Coyle
From : Tim Schattkowsky
Date : Sun Feb 27 2022 17:22:35

//Hello James,//

on *24.02.22* at *17:01:33* You wrote in Area *FTSC_PUBLIC*
to *Tim Schattkowsky* about *"Re: Re^4:  Directly include binary data in messages"*.

 JC> Synchronet and Mystic support direct BINKP over SSL natively which is a
 JC> good start to securing transmission.  At one point I had a opportunistic
 JC> SSL version of BinkP as well.

That already helps a lot. Have to add this. However, this in the end requires some additional information for the clients to connect to be aware of SSL/TLS support !?

 JC> Of course SSL doesn't stop routed netmail from being read by a SysOp in

Thats the point. Still, it keeps the direct listeners away. 

 JC> the middle though, so in this case Mystic does AES-256 encrypted netmail
 JC> if its setup with an encryption key for the address being netmailed.

The key distribution is the interesting part. Also, probably one should probably employ a combination of asym/sym (e.g., RSA+AES) as usal, so the symmetric keys are used only once.

Regards,
Tim

--- WinPoint 401.1
 * Origin: Original WinPoint Origin! (2:240/1120.29)

.