Subj : Re: binkd crypt
To   : tenser
From : esc
Date : Tue Jan 02 2024 01:49 pm

 te>  Nu> You can essentially do it with any system in which you can put a TLS
 te>  Nu> terminating proxy in the middle. Problem is, it doesn't matter at all
 te>  Nu> when you're talking to a bunch of other non-encrypted systems, so the
 te>  Nu> isn't really much of a point IMO.
 te> 
 te> Oh, I don't know: incremental progress towards security as a
 te> goal may be slow, but is still progress, no?

Y'know, I always thought an FTN that was locked down to encrypted comms only would be kinda neat. Like, each node uses TLS, and the sysops of each BBS have to vet the users to give access to the conferences for that net. On top of that, maybe there could be a requirement that for the user to access the confs (in addition to security level) they'd need to be connected via SSH or secure websocket. Could be neat...

But also there could be someone accidentally misconfiguring something somewhere and burping a bunch of messages from one net into another. Or someone could gate everything to their Synchronet web message base. Any number of things. :P So I guess for this net to work, it'd have to be small.

Anyway it's an interesting thought exercise.

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
 * Origin: m O N T E R E Y b B S . c O M (21:4/173)

.