Hello there!

I have a Mystic board running in a local Ubuntu Virtual Machine that I'm moving to a dedicated Raspberry Pi 5. I've pretty much got everything moved over and ready to flip the switch, except I'm running into issues getting cryptlib setup on the Pi. It works fine on Ubuntu, but it looks like gcc 9 isn't readily available for the Pi OS.

I tried two things so far:

1.) I compiled the latest version of cryptlib. Everything compiled fine, mystic detected it, created the ssl.cert, listened on port 22 for connections. But the connection handshake ends up failing with an error code that I should have written down lol

2.) I tried compiling the recommended (older) version of cryptlib with the latest gcc. That failed instantly.

I've seen some suggestions unrelated to cryptlib to download the gcc source and compile it on the Pi. These suggestions also
mention it takes upwards of 6+ hours to compile. That would be fine, but I'm wondering if anyone else has had any success going
down this route before I go sink a big chunk of time doing that. Maybe there's another way...?

If it comes down to it, I can just use an ssh tunnel for secure sysop access. But I like the thought of others being able to ssh in to the board as well.

Thanks in advance if anyone has any ideas!

Gabe

... Old musicians never die. They just decompose!

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Dark Side (21:3/234)

I have a Mystic board running in a local Ubuntu Vir

tual Machine that I'mGR> moving to a dedicated Raspberry
Pi 5. I've pretty much got everythingGR> moved over and
ready to flip the switch, except I'm running into issues

getting cryptlib setup on the Pi. It works fine on Ubuntu, but it

looksGR> like gcc 9 isn't readily available for the Pi
OS.I have an update. Still
no luck on the Pi 5 after rebuilding the system m
orethan a handful of times with various versions of the
OS, including Ubuntufor ARM.
I did discover that the doors that use the IR RLogin comm
and werethrowing EAccessViolations and went
down that rabbit hole for quite a bit.B
ut what HAS worked for me - I setup a
Pi 1 Qemu emulator using a Raspbian
build from 2019. Installed Mystic, c
ompiled cryptlib, and everything seemedto work
, even the doors.My idea i
s to buy an older Pi and setup Mystic there.
I could use the newer Pi5 as a m
edia server in the meantime.A question
for those who are running Mystic on RPi's:
SEEN-BY: 1/100 101 102 103 105 106 107 108 109 110 111 112 113 114 116 117 118 SEEN-BY: 1/119 120 121 122 124 125 126 127 128 129 130 131 133 136 137 138 139 SEEN-BY: 1/140 141 142 143 144 145 146 147 148 149 150 152 153 155 156 157 158 SEEN-BY: 1/159 160 161 162 163 164 166 168 169 171 172 173 174 175 176 177 178 SEEN-BY: 1/179 181 182 183 186 187 188 189 190 191 193 194 195 197 198 199 200 SEEN-BY: 1/201 202 203 204 205 206 207 208 210 211 212 213 214 215 216 217 218 SEEN-BY: 1/219 220 222 223 224 225 226 227 228 229 230 231 232 234 235 236 237 SEEN-BY: 1/238 239 240 241 242 244 245 246 247 248 249 616 995 999 2/100 116 SEEN-BY: 2/1202 3/100 102 105 107 109 110 111 113 119 120 126 127 135 137 141 SEEN-BY: 3/156 158 165 168 169 172 174 176 182 183 184 185 189 191 193 194 195 SEEN-BY: 3/196 199 201 202 203 204 205 206 207 208 211 212 214 215 216 217 219 SEEN-BY: 3/220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 SEEN-BY: 4/100 105 106 5/100 101

I have an update. Still no luck on the Pi 5 after rebuilding the system mo than a handful of times with various versions of the OS, including Ubuntu for ARM. I did discover that the doors that use the IR RLogin command were throwing EAccessViolations and went down that rabbit hole for quite a bit.

But what HAS worked for me - I setup a Pi 1 Qemu emulator using a Raspbian build from 2019. Installed Mystic, compiled cryptlib, and everything seeme to work, even the doors.

Sorry for the spam, but one more update - I may have answered my own question.

I got everything (I think?) to work on the Pi OS Buster distro, which can still be installed on a Pi 4 but not 5. For whatever reason, something about Pi 5 breaks certain things in mystic.

Still definitely curious if anyone has had any luck getting mystic running on Pi 5.

-grim

... THE fIRST sTEP iS tO tAKE oFF tHE cAPS lOCK

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Dark Side (21:3/234)

I have an update. Still no luck on the Pi 5 after rebuilding the system GR> GR> mo
than a handful of times with various versions of the OS, including Ubuntu for ARM. I did discover that the doors that use the IR RLogin command GR> GR> were
throwing EAccessViolations and went down that rabbit hole for quite a GR> GR> bit.

Lots of things don't work on my Pi 4."MIS POLL", "IR" (RLogin) and "IT" (Telnet) command. For that last two, i must use the external native LINUX shell commands.

... A friend is another self (Latin proverb)

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

I got everything (I think?) to work on the Pi OS Buster distro, which
can still be installed on a Pi 4 but not 5. For whatever reason, something about Pi 5 breaks certain things in mystic.

I know other people have made mention that something hardware related changed on the pi5 that causes issues with a kernel....

I don't remember the specifics, but I'm sure you can google this online.

... I put a dollar in one of those change machines. Nothing changed.

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Clutch BBS * telnet://clutchbbs.com (21:1/199)

Re: [ANSI] Re: cryptlib and Raspberry Pi
By: GRiM to All on Wed Feb 25 2026 06:47 pm

Howdy,

Pi 5 as a media server in the meantime.
A question for those who are running Mystic on RPi's:
SEEN-BY: 1/100 179 2/100 116 3/100 102 105 107 109 110 111 113 119 120 126

Was just reading your message and noticed it was chopped off. I was concerned my new packet parser messed up something.

Thankfully, it wasnt me :)

Your packet, while it does have more messages is unparsable because it has a bunch of NULs in the middle of it:

00000740 66 6f 72 20 74 68 6f 73 65 20 77 68 6f 20 61 72 |for those who ar| 00000750 65 20 72 75 6e 6e 69 6e 67 20 4d 79 73 74 69 63 |e running Mystic| 00000760 20 6f 6e 20 52 50 69 27 73 3a 00 00 00 00 00 00 | on RPi's:......| 00000770 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000780 00 00 00 00 0d 1b 5b 41 1b 5b 37 39 43 20 1b 5b |......[A.[79C .[| 00000790 30 6d 65 1b 5b 42 1b 5b 38 31 44 1b 5b 33 33 6d |0me.[B.[81D.[33m| 000007a0 57 68 61 74 20 76 65 72 73 69 6f 6e 20 68 61 72 |What version har|

So not sure if it means you have a corrupt mail database, or if it is an issue with your version of Mystic...


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Good morning/evening!

So not sure if it means you have a corrupt mail database, or if it is an issue with your version of Mystic...

...δεσ∩

I tried doing something fancy by changing the color of the text for those 2 lines where I polled for info on RPi's (right where I think you're saying it cut off). I wanted to set it apart from the wall of text I was posting lol.

I don't know what I'm doing, so is it possible I used some bad ansi characters? I used the inline mystic ansi editor directly in the message editor.

-grim

... Don't sweat the petty things and don't pet the sweaty things

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Dark Side (21:3/234)

Re: Re: cryptlib and Raspberry Pi
By: GRiM to deon on Thu Feb 26 2026 07:03 am

Howdy,

I don't know what I'm doing, so is it possible I used some bad ansi characters? I used the inline mystic ansi editor directly in the message editor.

Nah, I think its a bug with Mystic. Most of the bad mail packets I've seen are generated by it. But your editing might of put a corrupt message in the database, which it happily exported out and sent...

I think you're using A48, and if I recall there were some issues with it, perhaps update to A49 (I think that's the latest).


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Lots of things don't work on my Pi 4."MIS POLL", "IR" (RLogin) and "IT" (Telnet) command. For that last two, i must use the external native
LINUX shell commands.

Good to know! Which version of the Pi OS are you using? I'm going to try Mystic on Buster directly on the hardware to see if it fixes those IR/IT and other issues like it did in the emulator.

-g

... Nine times out of ten the statisticians are wrong

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Dark Side (21:3/234)

Re: [ANSI] Re: cryptlib and Raspberry Pi
By: GRiM to All on Wed Feb 25 2026 06:47 pm

Howdy,

In the below message..

My idea is to buy an older Pi and setup Mystic there. I could use the newer Pi 5 as a media server in the meantime.
A question for those who are running Mystic on RPi's:
SEEN-BY: 1/100 179 2/100 116 3/100 102 105 107 109 110 111 113 119 120 126 127 SEEN-BY: 3/135 137 141 156 158 165 168 169 172 174 176 182 183 184 185

.. clrghouz generated a packet without an origin line (because the incoming packet didnt have one):

..
00000750: 74 68 6f 73 65 20 77 68 6f 20 61 72 65 20 72 75 [those who are ru] 00000760: 6e 6e 69 6e 67 20 4d 79 73 74 69 63 20 6f 6e 20 [nning Mystic on ] 00000770: 52 50 69 27 73 3a 0d 53 45 45 4e 2d 42 59 3a 20 [RPi's:.SEEN-BY: ] 00000780: 31 2f 31 30 30 20 31 37 39 20 32 2f 31 30 30 20 [1/100 179 2/100 ] 00000790: 31 31 36 20 33 2f 31 30 30 20 31 30 32 20 31 30 [116 3/100 102 10] ..

And sbbsecho mentioned it:
2026-02-26 12:17:32 FSX_MYS: Failed to parse Origin Line in message from GRiM (21:3/234) in packet from 21:3/100: /opt/sbbs/fido/inbound/000e09aa.pkt

However, when the message is rendered, the SEEN-BY lines are rendered as well.

I thought there was a discussion (in a fidonet echo) that Origin lines were optional in echomails, and I thought I recall a commit in Synchronet around it. Just wondering why I'm seeing the SEEN-BY lines as part of the message?

Does sbbsecho not discover the SEEN-BY lines if there is no origin line?

Should the packed message be assembled differently if there is no origin line (so that the SEEN-BY lines are recognised and not displayed as part of the message text)?


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

I think you're using A48, and if I recall there were some issues with it, perhaps update to A49 (I think that's the latest).

...δεσ∩

Good to know, thanks for the heads up! I will update now.

-grim

... The only place I want data loss is on my credit card!

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Dark Side (21:3/234)

Re: Re: cryptlib and Raspberry Pi
By: GRiM to Gods69 on Thu Feb 26 2026 07:25 am

Howdy,

Good to know! Which version of the Pi OS are you using? I'm going to try Mystic on Buster directly on the hardware to see if it fixes those IR/IT and other issues like it did in the emulator.

I'm running proxmox on CM5s. I dont run mystic...

I do use synchronet, which is in an LXC container at the moment, in docker. The docker image is based on debian bullseye.


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: cryptlib and Raspberry Pi
By: deon to GRiM on Fri Feb 27 2026 12:31 am

Howdy,

Good to know! Which version of the Pi OS are you using? I'm going to try Mystic on Buster directly on the hardware to see if it fixes those IR/IT and other issues like it did in the emulator.

I'm running proxmox on CM5s. I dont run mystic...

I answered your question even though it wasnt directed to me :) I got confused for a second - I need to go to bed ...


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

GRiM wrote to All <=-

I have an update. Still no luck on the Pi 5 after rebuilding the system mo than a handful of times with various versions of the OS, including Ubuntu for ARM. I did discover that the doors that use the IR RLogin command were throwing EAccessViolations and went down that rabbit hole for quite a bit.

But what HAS worked for me - I setup a Pi 1 Qemu emulator using a Raspbian build from 2019. Installed Mystic, compiled cryptlib, and everything seeme to work, even the doors.

Sorry for the spam, but one more update - I may have answered my own question.

I got everything (I think?) to work on the Pi OS Buster distro, which
can still be installed on a Pi 4 but not 5. For whatever reason, something about Pi 5 breaks certain things in mystic.

The "Buster" distro? Wow, that was released almost 7 years ago, and
went end-of-life more than 3 years ago.

Official Raspberry Pi OS runs on "Trixie" (Debian "stable" version
13.3). I have a Pi 4 here running it just fine.

You can get it here: https://www.raspberrypi.com/software/



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.34-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

The "Buster" distro? Wow, that was released almost 7 years ago, and
went end-of-life more than 3 years ago.

Official Raspberry Pi OS runs on "Trixie" (Debian "stable" version
13.3). I have a Pi 4 here running it just fine.

You can get it here: https://www.raspberrypi.com/software/

Yah, I know Buster is old. I have Trixie running on a pi 5 right now. Mystic runs on it, but there are some show stopping issues I need to resolve before I can pull the trigger on using it. Running Mystic on Buster seems to fix all those issues.

Are you running Mystic on Trixie without any issues?

... Do device drivers need a chauffeur's license?

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Dark Side (21:3/234)

Good to know! Which version of the Pi OS are you using? I'm going to
try Mystic on Buster directly on the hardware to see if it fixes those IR/IT and other issues like it did in the emulator.

Using the official (64bit) Pi OS based on Debian Bookworm v12.13
The latest is Trixie (v13)

... Teachers have class.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

perhaps update to A49 (I think that's the latest).

Good to know, thanks for the heads up! I will update now.

A49 don't work here on Pi4, even using an 32bit OS.

... Learn how to spell. Play Hack!

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

A49 don't work here on Pi4, even using an 32bit OS.

Interesting.. I'll be testing it on on Buster shortly.

... Press any key to continue or any other key to quit...

--- Mystic BBS v1.12 A49 2023/01/27 (Linux/64)
* Origin: The Dark Side (21:3/234)

Hello deon!

27 Feb 26 00:28, deon wrote to digital man:

I thought there was a discussion (in a fidonet echo) that Origin lines were optional in echomails,

Maybe in netmails? IIRC, in echomail the Origin line is mandatory, as it's a standard way to obtain the sender address.

Regards,
Jegor

--- msged/lnx 6.3 2026-02-22
* Origin: MsgEd TE is available for OS/2, Linux, NT and DOS! (21:3/228)

Re: Parsing of echomail without an origin
By: Jegor to deon on Thu Feb 26 2026 08:31 pm

Howdy,

Maybe in netmails? IIRC, in echomail the Origin line is mandatory, as it's a standard way to obtain the sender address.

I had the same opinion, but I was corrected.

As per FTS-0004

"Although the Origin line is not required by all Echomail processors, it is added by the Conference Mail System to ensure complete compatibility."


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Parsing of echomail without an origin
By: deon to digital man on Fri Feb 27 2026 12:28 am

Re: [ANSI] Re: cryptlib and Raspberry Pi
By: GRiM to All on Wed Feb 25 2026 06:47 pm

Howdy,

In the below message..

My idea is to buy an older Pi and setup Mystic there. I could use the newer Pi 5 as a media server in the meantime.
A question for those who are running Mystic on RPi's:
SEEN-BY: 1/100 179 2/100 116 3/100 102 105 107 109 110 111 113 119 120 126 127 SEEN-BY: 3/135 137 141 156 158 165 168 169 172 174 176 182 183 184 185

.. clrghouz generated a packet without an origin line (because the incoming packet didnt have one):

..
00000750: 74 68 6f 73 65 20 77 68 6f 20 61 72 65 20 72 75 [those who are ru] 00000760: 6e 6e 69 6e 67 20 4d 79 73 74 69 63 20 6f 6e 20 [nning Mystic on ] 00000770: 52 50 69 27 73 3a 0d 53 45 45 4e 2d 42 59 3a 20 [RPi's:.SEEN-BY: ] 00000780: 31 2f 31 30 30 20 31 37 39 20 32 2f 31 30 30 20 [1/100 179 2/100 ] 00000790: 31 31 36 20 33 2f 31 30 30 20 31 30 32 20 31 30 [116 3/100 102 10] ..

And sbbsecho mentioned it:
2026-02-26 12:17:32 FSX_MYS: Failed to parse Origin Line in message from GRiM (21:3/234) in packet from 21:3/100: /opt/sbbs/fido/inbound/000e09aa.pkt

However, when the message is rendered, the SEEN-BY lines are rendered as well.

I thought there was a discussion (in a fidonet echo) that Origin lines were optional in echomails, and I thought I recall a commit in Synchronet around it. Just wondering why I'm seeing the SEEN-BY lines as part of the message?

Does sbbsecho not discover the SEEN-BY lines if there is no origin line?

Correct, and it's a known issue: https://gitlab.synchro.net/main/sbbs/-/issues/828

Should the packed message be assembled differently if there is no origin line (so that the SEEN-BY lines are recognised and not displayed as part of the message text)?

I would argue that in today's age, origin lines are *not* optional, but I don't think there's an FidoNet standard to defend that position. So really, it's just an issue that SBBSecho needs to handle. Fortunately, it's a rare (and usually easily correctable) problem on the senders side.
--
digital man (rob)

Synchronet/BBS Terminology Definition #49:
JS = JavaScript
Norco, CA WX: 83.7°F, 45.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

GRiM wrote to Gamgee <=-

The "Buster" distro? Wow, that was released almost 7 years ago, and
went end-of-life more than 3 years ago.

Official Raspberry Pi OS runs on "Trixie" (Debian "stable" version
13.3). I have a Pi 4 here running it just fine.

You can get it here: https://www.raspberrypi.com/software/

Yah, I know Buster is old. I have Trixie running on a pi 5 right now. Mystic runs on it, but there are some show stopping issues I need to resolve before I can pull the trigger on using it. Running Mystic on Buster seems to fix all those issues.

Hmmm, OK. Must be GCC/lib compatibility issues, I would guess.

Are you running Mystic on Trixie without any issues?

No, not running Mystic at all. I use that Pi for other stuff on my
local LAN, and for loitering in IRC channels. ;-)




... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.34-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Re: Parsing of echomail without an origin
By: Digital Man to deon on Thu Feb 26 2026 04:39 pm

Howdy,

I would argue that in today's age, origin lines are *not* optional, but I don't think there's an FidoNet standard to defend that position. So really, it's just an issue that SBBSecho needs to handle. Fortunately, it's a rare (and usually easily correctable) problem on the senders side.

Yeah, I agree...

I might just force clrghouz to poetically create an Origin for those messages that dont have one - so that upstream parses dont render these SEEN-BY lines...


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Morning Gods69,

A49 don't work here on Pi4, even using an 32bit OS.

I can confirm A49 works fine on Pi4 running Buster. Got it setup on the actual hardware last night. MIS runs, the rlogin/telnet commands run, it's got gcc < 8.3 so no issue installing and using cryptlib/ssh.

I don't recommend using such an old OS - I'm just putting it out there. Maybe this info can help g00 figure out a fix in the future? Does he monitor these message bases, or should post this somewhere for him to see?

G

... No honey, I can't eat with the family. My computer gets lonely!

--- Mystic BBS v1.12 A49 2023/01/27 (Linux/64)
* Origin: The Dark Side (21:3/234)

I can confirm A49 works fine on Pi4 running Buster. Got it setup on the actual hardware last night. MIS runs, the rlogin/telnet commands run, it's got gcc < 8.3 so no issue installing and using cryptlib/ssh.

OK. Thanks. I think Mystic need to be recompile with the last version
of freePascal to work correctly on latest RPi OS.

... Belief is thought at rest.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Re: Re: cryptlib and Raspberry Pi
By: GRiM to All on Wed Feb 25 2026 09:35 pm

I am extremely happy now thayt I put Ubuntu 25.10 on my Pi 5. Just finished compiling and setting up Synchronet on it after deciding to switch from Mystic. Mystic and crypt were fine on it, just prefer the Synchronet setup.
--- SBBSecho 3.37-Linux
* Origin: Bayou Blog BBS - bayoublog.ddns.net (21:3/232)

I am extremely happy now thayt I put Ubuntu 25.10 o

n my Pi 5. JustJR> finished compiling and setting up Syn
chronet on it after deciding toJR> switch from Mystic. M
ystic and crypt were fine on it, just prefer theJR> Sync
hronet setup. --- SBBSecho 3.37-LinuxInteres
ting.. I definitely tried Ubuntu on 5
with mystic but something didn'twork for me
or I would have kept it. I think it was pro
bably the IR/ITmenu commands.
I should have made better notes. lol.
I've got some moresdcards coming in soon
, I'll do another test with Ubuntu
.-GRiM
... As I said before, I never repeat myself

--- Mystic BBS v1.12 A49 2023/01/27 (Raspberry Pi/32)
* Origin: The Dark Side (21:3/234)