Subj : Re: binkd crypt
To   : Al
From : NuSkooler
Date : Tue Jan 02 2024 07:26 pm


On Monday, January 1st Al muttered...
 Al> I brought this up in the BINKD echo a few years ago thinking we could 
 Al> make this a default behaviour, or at least make it easier to impliment.

I think the main issue is older software and setups with true retro hardware -- it's just not really viable to even perform TLS on that old hardware.

For a true encrypted exprerience, we need a new protocol that is *always* encrypted. Of course you can't stop people from exporting to non-encrypted areas though, but it's a start.

-- 
|08 ■ |12NuSkooler |06// |12Xibalba |08- |07"|06The place of fear|07"
|08 ■ |03xibalba|08.|03vip |08(|0344510|08/|03telnet|08, |0344511|08/|03ssh|08)
|08 ■ |03ENiGMA 1/2 WHQ |08| |03Phenom |08| |0367 |08| |03iMPURE |08| |03ACiDic
--- ENiGMA 1/2 v0.0.14-beta (linux; x64; 18.18.2)
 * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

.