----------------------------------------------------------------------------------
@MSGID: 55055.sync@1:103/705 2d5cc930
@REPLY: 51948.dove-syncdisc@12:1/2 2d49255c
@TZUTC: -0700
@PID: Synchronet 3.21a-Linux master/88b423313 Sep 29
2025 GCC 12.2.0
@TID: SBBSecho 3.30-Linux master/88b423313 Sep 29
2025 GCC 12.2.0
@COLS: 80
@BBSID: VERT
@CHRS: CP437 2
@FORMAT: flowed
@NOTE: FSEditor.js v1.105
Re: sbbsecho and bad packets
By: deon to Digital Man on Mon Oct 06 2025 01:07 pm
> Re: sbbsecho and bad packets
> By: Digital Man to deon on Sun Oct 05 2025 06:09 pm
>
> > Looks to me like the DateTime is missing the NUL terminator:
> > 00000040 79 02 79 02 00 00 00 00 30 33 20 4f 63 74 20 32 |y.y.....03
> > Oct 2| 00000050 35 20 20 30 37 3a 31 37 3a 34 37 20 41 6c 6c 00 |5
> > 07:17:47 All.|
>
> > > Why is SBBSecho marking them bad?
>
> > The sbbsecho.log should say the reason why, but it`s probably the same
> > reason.
>
> I didnt think DateTime was a null terminated string? Its 20 Bytes in the
> packed message header (FTS-0001.16 C.1).
>
> "A packed message has a number of fixed length
> fields followed by four null terminated strings."
>
> (those being: to/from/subject and text are null terminated).
>
> Or have a missed something?
FWIW, Tom Jenning`s Fido software (specifically, unpmsg() from
unpacket.c) would`ve barfed on any message without a NUL-terminated date/time as
well.
https://www.sensitiveresearch.com/Archive/FidoNet/index.html
It would would even trigger a buffer overflow (off-by-one) bug in his code!
Just something I came across that was probably related to this discussion.
--
digital man (rob)
Sling Blade quote #5:
Karl Childers (to father): You ought not killed my little brother...
Norco, CA WX: 85.6°F, 18.0% humidity, 4 mph WNW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.30-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 50/109 103/705 154/10 218/700 221/1
240/1120 280/464 301/1 113
SEEN-BY: 341/66 463/68 712/848 5000/111 5001/100
5020/101 715 848 1042 4441
SEEN-BY: 5020/12000 5030/49 1081 5060/900 5061/133
5075/128 5083/444
@PATH: 103/705 301/1 5020/1042 4441