Subj : Re: binkd crypt
To   : NuSkooler
From : Al
Date : Wed Jan 03 2024 02:10 am

> On Monday, January 1st Al muttered...
>> I brought this up in the BINKD echo a few years ago thinking we could
>> 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.

I'm not saying we should drop binkp or any protocol, it works so lets use it.

I'm saying we could also support binkps and use it when it's available if we want to do that.

> 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.

I am only thinking of the binkp server. I would like to operate my node as simply and as securely as possible and make it easy for all nodes to do that.

When you say a "true encrypted experience" are you speaking of BBSing as a whole, encrypt the entire process of user login read/post/reply and everything that follows?

That would be a fairly big goal, but also probably doable today if we took a fresh approach. That approach would change everything. We'd have to leave behind the older software and setups you speak of. This is the big challenge of FTN networks. We have always tried to move things forward in a backward
compatible way, for good reasons.

I don't see any reason not to do that and build things for today, today.

The BBS and FTN world is very retro and I doubt that anyone wants to lose that, or our old friends running old software or setups.

I would like to see binkps become more of a standard and be easily available to use by nodes who can use it. I think most eveyone could use it.

--- BBBS/Li6 v4.10 Toy-6
 * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

.