• Mystic BBS v1.12 Alpha 42 Released

    From g00r00@21:1/108 to All on Sat Feb 2 03:44:19 2019
    Mystic BBS v1.12 Alpha 42 released for Windows (32/64bit), Intel Linux (32/64bit), macOS (32/64bit), and ARM Linux (Raspberry Pi).

    www.mysticbbs.com

    --- Mystic BBS v1.12 A42 2019/02/01 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Avon@21:1/101 to g00r00 on Sun Feb 3 00:22:34 2019
    On 01 Feb 2019, g00r00 pondered and said...

    Mystic BBS v1.12 Alpha 42 released for Windows (32/64bit), Intel Linux (32/64bit), macOS (32/64bit), and ARM Linux (Raspberry Pi).

    I will hatch these out to fsx_myst shortly...

    Best, Paul

    --- E:avon@bbs.nz ------ W:bbs.nz ---
    --- K:keybase.io/avon --------------

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From MeaTLoTioN@21:1/158 to g00r00 on Sat Feb 2 12:38:22 2019
    On 02/01/19, g00r00 said the following...

    Mystic BBS v1.12 Alpha 42 released for Windows (32/64bit), Intel Linux (32/64bit), macOS (32/64bit), and ARM Linux (Raspberry Pi).

    www.mysticbbs.com

    WOOHOO. Ok question for anyone reading who can help, not aimed directly at
    the g00r00; I am on A39, can I update directly to A42? I downloaded the A42 (Linux 64 bit) and read the update notes. From what I understand I have to update to A40 first, then A41, then A42? Is that right?

    Also seeing as I am on A39, what will I need to do (other than backup of
    course lol) in order to make the update go smoothly, not break anything,
    etc... and what "Gotcha's" should I expect to see happen?

    Thanks guys



    Best regards,
    Christian aka MeaTLoTioN

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)
  • From Avon@21:1/101 to MeaTLoTioN on Sun Feb 3 02:51:11 2019
    On 02 Feb 2019 at 07:38a, MeaTLoTioN pondered and said...

    WOOHOO. Ok question for anyone reading who can help, not aimed directly
    at the g00r00; I am on A39, can I update directly to A42? I downloaded
    the A42 (Linux 64 bit) and read the update notes. From what I understand
    I have to update to A40 first, then A41, then A42? Is that right?

    Just read the notes and ensure you take any unique steps you are required to
    do with each step between alphas.

    [snip]

    .------------------------------------.
    | UPGRADING FROM 1.12 A40-A41 to A42 |-------------------------
    `------------------------------------'

    - Replace existing binaries with the new alpha binaries:

    mystic.exe
    mis.exe
    fidopoll.exe
    mutil.exe
    nodespy.exe
    qwkpoll.exe
    upgrade.exe
    mplc.exe (in scripts directory)
    mide.exe (in scripts directory)

    .--------------------------------.
    | UPGRADING FROM 1.12 A39 to A40 |-------------------------
    `--------------------------------'

    - Replace existing binaries with the new alpha binaries:

    mystic.exe
    mis.exe
    fidopoll.exe
    mutil.exe
    nodespy.exe
    qwkpoll.exe
    upgrade.exe
    mplc.exe (in scripts directory)
    mide.exe (in scripts directory)

    - If you use default installation replace the default.txt from DATA with the
    newer one, otherwise the following prompts have been modified or changed
    and will need to be updated/added to your custom themes:

    Changed prompts: 18, 419, 420, 463, 486
    New prompts: 538-552

    - Copy "msg_index.ini" from the TEXT folder into your TEXT folders
    - Copy "msg_index.ans" from the TEXT folder into your TEXT folders
    - Copy "msg_index_help.ans" from the TEXT folder into your TEXT folders

    - Copy "cfgroot4.ans" from the DATA folder into your DATA folder

    - Execute upgrade.exe

    - Recompile MPL programs

    [snip]

    So in the jump from A39 to A40/41 there are a few extra things to do... as
    per above, but then the jump to A41 is really only updating some .exe files...

    so yes, you can move from A39 to A42 in one hit, just update the .exe files
    (as they are the same things you need to do for both steps outlined above)
    but also do the extra steps detailed in the A39 to A40/41 notes.

    Hope that helps, and remember to back up first :)

    Best, Paul

    --- E:avon@bbs.nz ------ W:bbs.nz ---
    --- K:keybase.io/avon --------------

    --- Mystic BBS v1.12 A42 2019/02/01 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to g00r00 on Sun Feb 3 03:04:51 2019
    On 01 Feb 2019 at 10:44p, g00r00 pondered and said...

    Mystic BBS v1.12 Alpha 42 released for Windows (32/64bit), Intel Linux (32/64bit), macOS (32/64bit), and ARM Linux (Raspberry Pi).

    + Prompt #464 message quote text now has &4 MCI code which is replaced by
    the time that the original message was written.

    Thanks for this :) I like it. Any chance a prompt could be created that would auto populate at the start of a new post in the FSE. It would be very similar to Prompt #464 but could be used optionally at the start of new messages being written?

    That way I could post in my body copy some opening liner that included the date/time I wrote the message. Just as I now am able to quote the date/time someone wrote something when I reply to them.

    Couple of niggles observed in the opening 60 mins since updating.

    1/100 polls 1/101 internally on the same PC and I noted the BinkP session on the 1/101 (Agency BBS) box got hung up with the server reporting the HUB was still connected when I could see it was not. The mis logs were full of the
    same error. I closed mis down on Agency and it borked with a data dump

    │ 21:15:43 BINKP 1-Error receiving data (Msg= Size=0/10364)
    │ 21:15:43 BINKP 1-Error receiving data (Msg= Size=0/10364)
    │ 21:15:43 BINKP 1-Error receiving data (Msg= Size=0/10364)
    │ 21:15:43 BINKP 1-Error receiving data (Msg= Size=0/10364)
    │ 21:15:43 MANAGER Shutdown complete └──────────────────────────────────────────────────────────────
    n unhandled exception occurred at $00444553:
    EInOutError: Invalid file handle
    $00444553
    $0040B0DB
    $0040B1AD
    $00444957
    $0040C05E
    $77711C95
    $0040DDE9
    $0040D8C6
    $0040DC4E
    $774EEFAC
    $77743618
    $777435EB

    The logs show this... lot's of it

    + 2019.02.02 21:15:42 BINKP 1-Error receiving data (Msg= Size=0/10364)
    + 2019.02.02 21:15:42 BINKP Read error 0-Not defined (-33) Bad message MAC
    for packet type 21, length 48
    + 2019.02.02 21:15:42 BINKP Read error 0-Not defined (-33) Bad message MAC
    for packet type 21, length 48
    + 2019.02.02 21:15:42 BINKP Read error 0-Not defined (-33) Bad message MAC
    for packet type 21, length 48

    After restarting I noticed when the HUB polled 1/101 again there was a different message.

    + 2019.02.02 21:32:45 BINKP 1-HostName AGENCY
    + 2019.02.02 21:32:45 BINKP 1-R: NUL SYS fsxHUB Risa [NET1]
    + 2019.02.02 21:32:45 BINKP 1-System fsxHUB Risa [NET1]
    + 2019.02.02 21:32:45 BINKP 1-S: NUL OPT TLS CRAM-MD5-3bc1b9ab0d7ce430e266024dbc6a3b4a
    + 2019.02.02 21:32:45 BINKP 1-R: NUL ZYZ Avon
    + 2019.02.02 21:32:45 BINKP 1-SysOp Avon
    + 2019.02.02 21:32:45 BINKP 1-S: NUL SYS Agency BBS
    + 2019.02.02 21:32:45 BINKP 1-S: NUL ZYZ Avon
    + 2019.02.02 21:32:45 BINKP 1-S: NUL TIME Sat, 02 Feb 2019 21:32:45 1300
    + 2019.02.02 21:32:45 BINKP 1-S: NUL VER Mystic/1.12A42 binkp/1.0
    + 2019.02.02 21:32:45 BINKP 1-S: NUL BUILD 2019/02/01 22:29:26 Windows/32
    + 2019.02.02 21:32:45 BINKP 1-S: ADR 46:3/203@agoranet 39:970/1@amiganet 3:770/100@fidonet 21:1/101@fsxnet 44:100/14@dorenet
    + 2019.02.02 21:32:45 BINKP 1-R: NUL TIME Sat, 02 Feb 2019 21:32:45 1300
    + 2019.02.02 21:32:45 BINKP 1-Info TIME Sat, 02 Feb 2019 21:32:45 1300
    + 2019.02.02 21:32:45 BINKP 1-R: NUL VER Mystic/1.12A42 binkp/1.0
    + 2019.02.02 21:32:45 BINKP 1-Mailer Mystic/1.12A42 binkp/1.0
    + 2019.02.02 21:32:45 BINKP 1-R: NUL BUILD 2019/02/01 22:29:50 Windows/32
    + 2019.02.02 21:32:45 BINKP 1-Info BUILD 2019/02/01 22:29:50 Windows/32
    + 2019.02.02 21:32:45 BINKP 1-R: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
    + 2019.02.02 21:32:45 BINKP 1-R: NUL TLS
    + 2019.02.02 21:32:45 BINKP 1-S: NUL TLS
    + 2019.02.02 21:32:45 BINKP 1-Activating SSL session
    + 2019.02.02 21:32:47 BINKP 1-R: PWD
    + 2019.02.02 21:32:47 BINKP 1-Authenticating 21:1/100@fsxnet by CRAM-MD5
    + 2019.02.02 21:32:47 BINKP 1-S: OK secure
    + 2019.02.02 21:32:47 BINKP 1-Queued 1 files for 21:1/100@fsxnet
    + 2019.02.02 21:32:47 BINKP 1-S: NUL QSIZE 1 files 593 bytes
    + 2019.02.02 21:32:47 BINKP 1-Sending: 00000001.saf (593 bytes)
    + 2019.02.02 21:32:47 BINKP 1-S: FILE 00000001.saf 593 1549143062 0
    + 2019.02.02 21:32:47 BINKP 1-R: NUL QSIZE 6 files 6,201,758 bytes
    + 2019.02.02 21:32:47 BINKP 1-Remote Queue: 6 files 6,201,758 bytes
    + 2019.02.02 21:32:47 BINKP 1-R: FILE 01a77fe9.pkt 122875 1549143146 0
    + 2019.02.02 21:32:47 BINKP 1-Receiving: 01a77fe9.pkt (122,875 bytes)
    + 2019.02.02 21:32:47 BINKP 1-R: GOT 00000001.saf 593 1549143062
    + 2019.02.02 21:32:47 BINKP 1-S: EOB
    + 2019.02.02 21:32:47 BINKP Connection dropped (Read error WSAECONNRESET: Connection was reset by the remote host executing a close)
    + 2019.02.02 21:32:47 BINKP 1-Error receiving data (Msg= Size=8123/18755)
    + 2019.02.02 21:32:47 BINKP 1-Connection lost
    + 2019.02.02 21:32:47 BINKP 1-Session ended (1 sent, 0 rcvd, 0 skip)
    + 2019.02.02 21:32:47 BINKP 1-Client shutting down

    I then turned off SSL for 1/101 at the HUB and the subsequent polls so far
    seem to be OK.

    + 2019.02.02 21:55:18 BINKP 1-HostName AGENCY
    + 2019.02.02 21:55:18 BINKP 1-R: NUL SYS fsxHUB Risa [NET1]
    + 2019.02.02 21:55:18 BINKP 1-System fsxHUB Risa [NET1]
    + 2019.02.02 21:55:18 BINKP 1-S: NUL OPT TLS CRAM-MD5-f49fd8c4ebe49d00c319f054628168a7
    + 2019.02.02 21:55:18 BINKP 1-R: NUL ZYZ Avon
    + 2019.02.02 21:55:18 BINKP 1-SysOp Avon
    + 2019.02.02 21:55:18 BINKP 1-S: NUL SYS Agency BBS
    + 2019.02.02 21:55:18 BINKP 1-S: NUL ZYZ Avon
    + 2019.02.02 21:55:18 BINKP 1-S: NUL TIME Sat, 02 Feb 2019 21:55:18 1300
    + 2019.02.02 21:55:18 BINKP 1-S: NUL VER Mystic/1.12A42 binkp/1.0
    + 2019.02.02 21:55:18 BINKP 1-S: NUL BUILD 2019/02/01 22:29:26 Windows/32
    + 2019.02.02 21:55:18 BINKP 1-S: ADR 46:3/203@agoranet 39:970/1@amiganet 3:770/100@fidonet 21:1/101@fsxnet 44:100/14@dorenet
    + 2019.02.02 21:55:18 BINKP 1-R: NUL TIME Sat, 02 Feb 2019 21:55:17 1300
    + 2019.02.02 21:55:18 BINKP 1-Info TIME Sat, 02 Feb 2019 21:55:17 1300
    + 2019.02.02 21:55:18 BINKP 1-R: NUL VER Mystic/1.12A42 binkp/1.0
    + 2019.02.02 21:55:18 BINKP 1-Mailer Mystic/1.12A42 binkp/1.0
    + 2019.02.02 21:55:18 BINKP 1-R: NUL BUILD 2019/02/01 22:29:50 Windows/32
    + 2019.02.02 21:55:18 BINKP 1-Info BUILD 2019/02/01 22:29:50 Windows/32
    + 2019.02.02 21:55:18 BINKP 1-R: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
    + 2019.02.02 21:55:18 BINKP 1-R: PWD
    + 2019.02.02 21:55:18 BINKP 1-Authenticating 21:1/100@fsxnet by CRAM-MD5
    + 2019.02.02 21:55:18 BINKP 1-S: OK secure
    + 2019.02.02 21:55:18 BINKP 1-Queued 0 files for 21:1/100@fsxnet
    + 2019.02.02 21:55:18 BINKP 1-S: NUL QSIZE 0 files 0 bytes
    + 2019.02.02 21:55:18 BINKP 1-S: EOB
    + 2019.02.02 21:55:18 BINKP 1-R: NUL QSIZE 1 files 688 bytes
    + 2019.02.02 21:55:18 BINKP 1-Remote Queue: 1 files 688 bytes
    + 2019.02.02 21:55:18 BINKP 1-R: FILE 01a99281.pkt 688 1549144504 0
    + 2019.02.02 21:55:18 BINKP 1-Receiving: 01a99281.pkt (688 bytes)
    + 2019.02.02 21:55:18 BINKP 1-S: GOT 01a99281.pkt 688 1549144504
    + 2019.02.02 21:55:19 BINKP 1-R: EOB
    + 2019.02.02 21:55:19 BINKP 1-Session ended (0 sent, 1 rcvd, 0 skip)
    + 2019.02.02 21:55:19 BINKP 1-Client shutting down

    Best, Paul

    --- E:avon@bbs.nz ------ W:bbs.nz ---
    --- K:keybase.io/avon --------------

    --- Mystic BBS v1.12 A42 2019/02/01 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to MeaTLoTioN on Sun Feb 3 01:46:00 2019
    On 02-02-19 07:38, MeaTLoTioN wrote to g00r00 <=-

    On 02/01/19, g00r00 said the following...

    Mystic BBS v1.12 Alpha 42 released for Windows (32/64bit), Intel Linux (32/64bit), macOS (32/64bit), and ARM Linux (Raspberry Pi).

    www.mysticbbs.com

    WOOHOO. Ok question for anyone reading who can help, not aimed directly
    at the g00r00; I am on A39, can I update directly to A42? I downloaded
    the A42 (Linux 64 bit) and read the update notes. From what I
    understand I have to update to A40 first, then A41, then A42? Is that right?

    You can upgrade directly to A42. Check the upgrade.txt for the required steps to do so.

    Also seeing as I am on A39, what will I need to do (other than backup
    of course lol) in order to make the update go smoothly, not break anything, etc... and what "Gotcha's" should I expect to see happen?

    Read upgrade.txt for the details. It's well documented.


    ... BATCH - A group, kinda like a herd.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From g00r00@21:1/108 to Avon on Sat Feb 2 12:38:40 2019
    After restarting I noticed when the HUB polled 1/101 again there was a different message.

    Please keep TLS off for BINKP for now, it doesn't work reliably yet. I will make a patch note when I am able to reproduce the problem and fix it. For now I've labeled it "experimental" in the configuration, and its best to just leave it off.

    The issues seem to be centered around latency as far as I can tell, so I need to find the time to set up a test. Testing between two local installations of Mystic seems to work every time for me, so I need to set up a system I can
    test from outside my network.

    A42 was a little spur of the moment, there were a couple of bigger bugs that needed to be fixed for Pi users who don't have the "luxury" of having regular pre-alpha builds so I wasn't able to get to fixing this up yet.

    --- Mystic BBS v1.12 A42 2019/02/01 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Avon@21:1/101 to g00r00 on Sun Feb 3 14:08:35 2019
    On 02 Feb 2019 at 07:38a, g00r00 pondered and said...

    Please keep TLS off for BINKP for now, it doesn't work reliably yet. I will make a patch note when I am able to reproduce the problem and fix
    it. For now I've labeled it "experimental" in the configuration, and
    its best to just leave it off.

    Noted, thanks.

    Best, Paul

    --- E:avon@bbs.nz ------ W:bbs.nz ---
    --- K:keybase.io/avon --------------

    --- Mystic BBS v1.12 A42 2019/02/01 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106 to Avon on Sat Feb 2 21:43:12 2019
    On 02 Feb 2019 at 07:38a, g00r00 pondered and said...

    Please keep TLS off for BINKP for now, it doesn't work reliably yet. I will make a patch note when I am able to reproduce the problem and fix it. For now I've labeled it "experimental" in the configuration, and
    its best to just leave it off.

    Noted, thanks.

    My Mystic is also upgraded. If you'd like to do some testing to see how Mystic would behave as a hub we could do that. I could setup a node in Z1 and we could
    see what happens between zones. It'd be a good test if we had nodes in Z2 and 4 as well.

    I know that is something you were pondering about so we can have a closer look if you wanted.. :)

    --- BBBS/Li6 v4.10 Toy-3
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From bcw142@21:1/145.2 to Avon on Sun Feb 3 01:18:30 2019
    On 01 Feb 2019, g00r00 pondered and said...

    Mystic BBS v1.12 Alpha 42 released for Windows (32/64bit), Intel Linu (32/64bit), macOS (32/64bit), and ARM Linux (Raspberry Pi).

    I will hatch these out to fsx_myst shortly...

    Best, Paul

    Yup, hatched and working ;) Just using A42 x64 Linux Release version to send this, so it works. I'll update my Pi this weekend (still Saturday here), and then my Windows 10 Sunday. Looks good, seeing more and more fixes working
    like killing of ghost nodes and such. Still getting hammered with things like 2628 NNTP requests in less that 1 second to my Pi, that wears it down in
    about a week and the web server goes crazy (really begins to hang and not process requests). That's not due to NNTP requests, of course. Created a
    script for slowness and hangs I called Break:
    #!/bin/bash
    # break - break mis run
    sudo killall mis
    sleep 12
    sudo /mystic/mis daemon

    The hacking gets thrown off by that for a few hours at least and it clears
    the hangs that happen after a week or so (that stops my Vampire Snowman bot). Time to make more bots for different days with different characters ;)
    Will take some time to get ssh working again with the new changes in the cryptlib. Still have the old one running on the Pi and ssh not working here
    on AlphaTest. Will likely get it running under Windows 10 first as that's far easier to do.

    --- Mystic BBS v1.12 A42 2019/02/01 (Linux/64)
    * Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)