Subj : Re: Is binkp/d's security model kaputt?
To   : tenser
From : deon
Date : Thu Sep 23 2021 08:04 am

  Re: Re: Is binkp/d's security model kaputt?
  By: tenser to deon on Thu Sep 23 2021 02:06 am

 > On 22 Sep 2021 at 05:47p, deon pondered and said...
 >
 >
 >  de> IE: if you specify a packet version, your HTTP post will give you a
 >  de> binary "bundle" of messages. If not, you get a json collection of
 >  de> mesages. That way, "old" systems can get packets that can be used by
 >  de> their old software, but something like wget could get their bundles. For "new" systems, it'll be a more
 >
 > Whoa, time out here.  This is conflating two things: the transport
 > protocol, and the thing being transported.  This is a mistake that
 > the BBS people made and continue to make.
 >
 > But HTTP has an answer for this: you add a `Content-Type:` header
 > to the HTTP request (or response) that can tell you exactly what
 > the message contains.

No timeout needed yet.

There are probably many ways to skin this cat. The Accept/Content-Type headers are but one and probably the way I'd be implementing it.

Since I'm not there yet, I'll happily watch and read on how others think about doing it.

 > The thing to do here is define a small taxonomy of X- tokens
 > describing various BBS-centric formats and follow what the header
 > says.

Sure, lets muse over that list here...


....лоеп
--- SBBSecho 3.14-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.