1. Forum
  2. Fidonet
  3. MBSE

  • MBSE 1.0.7.22 upgrade

    From Vincent Coen@2:250/1 to All on Tue May 25 16:07:12 2021
    Hello All!

    This is a WARNING for all those that upgrade to this version :

    You MUST go to 1.11.21 and set this on.

    Despite it only tossing pkt's in var/inbound. If not it will leave all .pkt and
    .PKT alone with no hint what so ever why in the log files. In my case these pkt's are from valid uplinks.

    Note in my system var/inbound is set for both protected and not under option 1.4.2 & .3.

    Vincent

    --- Mageia Linux v7.1 X64/Mbse v1.0.7.21/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Andrew Leary@1:320/219 to Vincent Coen on Tue May 25 16:28:44 2021
    Hello Vincent!

    25 May 21 16:07, you wrote to all:

    Despite it only tossing pkt's in var/inbound. If not it will leave all .pkt and .PKT alone with no hint what so ever why in the log files. In
    my case these pkt's are from valid uplinks.

    Note in my system var/inbound is set for both protected and not under option 1.4.2 & .3.

    This is defeating the purpose of having a separate inbound for secure sessions. The new feature is not needed in your setup; as all packets would end up being tossed anyway. Having both inbounds set to the same path is NOT RECOMMENDED as it will leave your system vulnerable to mail bombs.

    Regards,

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Vincent Coen@2:250/1 to Andrew Leary on Mon May 31 13:29:21 2021
    Hello Andrew!

    Tuesday May 25 2021 16:28, you wrote to me:

    Hello Vincent!

    25 May 21 16:07, you wrote to all:

    Despite it only tossing pkt's in var/inbound. If not it will
    leave all .pkt and .PKT alone with no hint what so ever why in
    the log files. In my case these pkt's are from valid uplinks.

    Note in my system var/inbound is set for both protected and not
    under option 1.4.2 & .3.

    This is defeating the purpose of having a separate inbound for secure sessions. The new feature is not needed in your setup; as all packets
    would end up being tossed anyway. Having both inbounds set to the
    same path is NOT RECOMMENDED as it will leave your system vulnerable
    to mail bombs.

    Point made, I have now changed it (1.4.10.2) to ./var/unknown and turned off 1.11.21 to see what happens in my inbound area regarding *.PKT's however the packets coming in are from a known system.


    Vincent
    --- Mageia Linux v7.1 X64/Mbse v1.0.7.21/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)