1. Forum
  2. FidoNet
  3. WINDOWS

  • Crap

    From Tommi Koivula@2:221/6 to All on Saturday, March 23, 2024 12:51:48
    Hi All,

    Some crap messages generated in this echo at 2:221/360 due to husky/sqpack crash. However, sqpack should have not run in this echo, but due to the bug in husky/sqpack it was run.

    Sorry about that.

    'Tommi

    ---
    * Origin: news://news.fidonet.fi (2:221/6.0)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Saturday, March 23, 2024 12:18:54
    Hi Tommi,

    On 2024-03-23 12:51:48, you wrote to All:

    Some crap messages generated in this echo at 2:221/360 due to
    husky/sqpack crash. However, sqpack should have not run in this echo,
    but due to the bug in husky/sqpack it was run.

    Thanks for testing my tosser:

    ------------ Fri 2024-03-22, FMail-lnx64-2.3.0.1-Beta20240319
    20:21:12.541 Toss
    20:21:12.544 Processing 6b0c7778.pkt from 2:221/0 to 2:280/464
    20:21:12.544 Pkt info: HPT 1.9, Type 2+, 1620, 2024-03-22 20:20:44, Pwd, Sec 20:21:12.544 Skipping garbage in PKT file...
    20:21:12.548 Skipping garbage in PKT file...
    ...
    20:21:12.582 Netmail: 0, Personal: 0, Hudson: 1, JAMbase: 1
    20:21:12.582 Msgbase net: 0, echo: 1, dup: 0, bad: 1


    ------------ Fri 2024-03-22, FMail-lnx64-2.3.0.1-Beta20240319
    20:22:13.235 Toss
    20:22:13.239 Processing 6b0c7781.pkt from 2:221/0 to 2:280/464
    20:22:13.239 Pkt info: HPT 1.9, Type 2+, 1320, 2024-03-22 20:22:02, Pwd, Sec ...
    20:22:13.266 Processing jam area: WINDOWS
    20:22:13.268 *** Encountered a problem during JAM base maintenance, area WINDOWS
    20:22:13.268 Updating reply chains: End

    I've never seen that last error before.

    I think there is room for improvement. Like not keep on tossing the contents of a pkt file when garbage is encountered... ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Saturday, March 23, 2024 13:32:53
    * Originally in WINDOWS
    * Crossposted in FMAIL_HELP

    Hi Wilfred.

    23 Mar 24 12:18, you wrote to me:

    Some crap messages generated in this echo at 2:221/360 due to
    husky/sqpack crash. However, sqpack should have not run in this
    echo, but due to the bug in husky/sqpack it was run.

    Thanks for testing my tosser:

    You're welcome. :/

    20:22:13.266 Processing jam area: WINDOWS
    20:22:13.268 *** Encountered a problem during JAM base maintenance,
    area WINDOWS
    20:22:13.268 Updating reply chains: End

    I've never seen that last error before.

    I think there is room for improvement. Like not keep on tossing the contents of a pkt file when garbage is encountered... ;-)

    Some AI needed to detect "crap" ;-)

    --- FMail-lnx64 2.3.0.1-B20240319

    'Tommi

    --- FMail-lnx64 2.3.0.2-B20240323
    * Origin: -------------------> (2:221/6.600)
  • From August Abolins@2:221/1.58 to Tommi Koivula on Sunday, March 24, 2024 10:01:00
    Hello Tommi!

    ** On Saturday 23.03.24 - 13:32, Tommi Koivula wrote to Wilfred van Velzen:

    I think there is room for improvement. Like not keep on
    tossing the contents of a pkt file when garbage is
    encountered... ;-)

    Some AI needed to detect "crap" ;-)

    Or.. simply not toss a pkt if at least the msg header is
    malformed?

    Those messages apparently failed to have normal header
    structure.
    --
    ../|ug

    --- OpenXP 5.0.58
    * Origin: (2:221/1.58)
  • From Tommi Koivula@2:221/1.1 to August Abolins on Sunday, March 24, 2024 20:07:30
    Hi August.

    24 Mar 24 10:01:00, you wrote to me:

    I think there is room for improvement. Like not keep on
    tossing the contents of a pkt file when garbage is
    encountered... ;-)

    Some AI needed to detect "crap" ;-)

    Or.. simply not toss a pkt if at least the msg header is
    malformed?

    Yes. But some intelligence needed to detect garbage. :)

    'Tommi

    ---
    * Origin: Point One (2:221/1.1)
  • From Carlos Navarro@2:341/234.1 to Wilfred van Velzen on Sunday, March 24, 2024 20:08:18
    23 Mar 2024 12:18, you wrote to Tommi Koivula:

    ...
    20:22:13.266 Processing jam area: WINDOWS
    20:22:13.268 *** Encountered a problem during JAM base maintenance,
    area WINDOWS
    20:22:13.268 Updating reply chains: End

    I've never seen that last error before.

    I've found that same error in my logs, after every toss. It seems it stopped after Tommi posted his message explaining the issue.

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada (2:341/234.1)
  • From August Abolins@1:396/45.29 to Tommi Koivula on Sunday, March 24, 2024 16:07:00
    Hello Tommi!

    Or.. simply not toss a pkt if at least the msg header is
    malformed?

    Yes. But some intelligence needed to detect garbage. :)

    The malformed messages bypassed OpenXP's checks and balances
    even though there is a general pkt-format check. So.. you're
    absolutely right.. more needs to be done. Otherwise, it looks
    like FTN can be hacked for worse outcomes very easily.

    --
    ../|ug

    --- OpenXP 5.0.58
    * Origin: (1:396/45.29)