Subj : RE: binkps
To   : Oli
From : NuSkooler
Date : Sat Apr 11 2020 12:56 pm


On Saturday, April 11th Oli muttered...
 Ol> TLS support in binkd would be nice, but for incoming connections I would 
 Ol> still use nginx or haproxy for TLS termination.

+1 for TLS termination. nginx/HAProxy/Caddy/etc. are all heavily peer reviewed 
in terms of security. Various BBS packages are not. I had to enable some older 
cipher suites and lessen security just to allow some paritcular BBS terminals 
to connect to my b
....just kind of jumping in here. What did the "binkps" proto end up looking 
like? Just bink proxied over TLS? I'd like to get this set up (I'll be TLS 
terminating with Caddy personally)





-- 
>> NuSkooler
>> Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
>> ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
--- ENiGMA 1/2 v0.0.11-beta (linux; x64; 12.13.1)
 * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

.