= Сообщение: 6454 из 7128 ====================================== FTSC_PUBLIC = От : Alexey Vissarionov 2:5020/545 22 Mar 22 01:55:50 Кому : Tim Schattkowsky 22 Mar 22 01:55:50 Тема : Directly include binary data in messages FGHI : area://FTSC_PUBLIC?msgid=2:5020/545+62390677 На : area://FTSC_PUBLIC?msgid=2:240/1120.29+4dbdfe80 = Кодировка сообщения определена как: CP866 ================================== Ответ: area://FTSC_PUBLIC?msgid=2:240/1120.29+4dbdfe90 ============================================================================== Good ${greeting_time}, Tim!
21 Mar 2022 22:33:52, you wrote to BjФrn Felten:
TS>>> BTW: RFC8314 suggests already in the introduction that for TS>>> email, implicit TLS should be preferred over STARTTLS :) BF>> I've been following this thread for some time, and I don't BF>> understand how it concerns our FTN network. TS> You probably missed that we (no matter what the subject says) TS> actually discussed, how BinkP connections can be secured by TLS?
TLS is not about the security - it is (really "was") mostly about the mutual authentification. It could work as designed (in the era of SSL 2.0 and before), but the emerge of HTTPS killed some key features of it.
TS> Unless I missed something, the messages people write are currently TS> mostly transported using BinkP, which makes this sort of relevant.
You appear to be missing the key point: binkp is defined by its' reference implementation (binkd), and the FTS-1026 plays the secondary role.
#include <FTA-1006>
Yes, it _may_ support SSL/TLS. Yes, it _may_ even share the inbound port with HTTPS. Yes, it _may_ be set up to circumvent most barriers in the modern Internet.
But if you want to implement some of these features somewhere else, you _must_ know how that's implemented in binkd.
-- Alexey V. Vissarionov aka Gremlin from Kremlin gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii