Has anyone managed to get cryptlib to work successfully for Mystic under Debian 12?
I've tried building 3 or 4 different versions of it and although they build ok I can't ssh to mystic under debian12 with cryptlib 3.4.x
Hey y'all,
Has anyone managed to get cryptlib to work successfully for Mystic under Debian 12?
I've tried building 3 or 4 different versions of it and although they build ok I can't ssh to mystic under debian12 with cryptlib 3.4.x
Anyone managed to get it to work? Specifically on Debian 12, not Ubuntu
or anything else similar.
Try building it as per the note on the wiki page using I believe gcc v9 instead of 10 or 8 in place of 9.. I have it running on my Debian 12
with no issues.
Yep, running 3.4.5 (the only one that seems to work with Mystic) here on Debian 12 on x86_64 (amd64).
Try stopping MIS, removing data/ssl.cert and then restarting MIS. If I remember correctly the self-signed certificate left-overs can cause trouble...
Has anyone managed to get cryptlib to work successfully for Mystic
under Debian 12? I've tried building 3 or 4 different versions of it
and although they build ok I can't ssh to mystic under debian12 with cryptlib 3.4.x
Anyone managed to get it to work? Specifically on Debian 12, not
Ubuntu or anything else similar.
Hmm I tried installing the gcc9 as per the wiki but it doesn't appear to be available in the debian 12 repos anymore;
Try this -- the build problems with newer versions of gcc (e.g. 12) are simply due to an obsolete version check, and can easily be circumvented without resorting to older gcc versions:
https://scbbs.nsupdate.info/files/cryptlib.txt
(Linking to this as the patch "file" might get mauled by line breaks
etc.)
Hope this helps!
On 08 Jan 2024, Zip said the following...
Try this -- the build problems with newer versions of gcc (e.g. 12) a simply due to an obsolete version check, and can easily be circumvent without resorting to older gcc versions:
https://scbbs.nsupdate.info/files/cryptlib.txt
(Linking to this as the patch "file" might get mauled by line breaks etc.)
Hope this helps!
Thanks, just used the patch line with the already downloaded cl345.zip from previous attempts, and giving a build a go and will let you know
how it goes =)
I knew it would be something simple without having to use an older
version of gcc =)
Yeah I tried that, but gcc9 isn't available in the debian 12 repos, they may have been at some point in the past but not now it seems.
# apt-get install gcc-9 g++-9
Well that didn't work either, for some reason it's not creating a
ssl.cert file in /mystic/data - I checked all the perms are ok which
they are, I think that's probably my issue, not that CL isn't actually working.
Try building it as per the note on the wiki page using I believe gcc instead of 10 or 8 in place of 9.. I have it running on my Debian 12 with no issues.
Yeah I tried that, but gcc9 isn't available in the debian 12 repos, they may have been at some point in the past but not now it seems.
Did that other workaround I sent you work in the mean time?? It did on my Debian install..
Try upgrading Mystic. Looks like you're using an A48 alpha before A48 was released as a stable version, and most of the people that do seem to
have it working are at the stable version of A48 or in the A49 alphas. There's always the possibility SSH (or whatever one has a problem with
at the time while using an old version) was being worked on at that
time, and it's damn near impossible to try to help people while using stuff that technically isn't even supported any more (g00 may support
A48 stable but may also try to convince you to upgrade to the latest
alpha to see if your problem was already fixed).
On 08 Jan 2024, Accession said the following...
Try upgrading Mystic. Looks like you're using an A48 alpha before A48 released as a stable version, and most of the people that do seem to have it working are at the stable version of A48 or in the A49 alphas There's always the possibility SSH (or whatever one has a problem wit at the time while using an old version) was being worked on at that time, and it's damn near impossible to try to help people while using stuff that technically isn't even supported any more (g00 may support A48 stable but may also try to convince you to upgrade to the latest alpha to see if your problem was already fixed).
Yeah I will give that a go and see if it helps, thanks for the advice, I have been meaning to do that for some time, but always put it off until "the crunch time" lol.
Well that didn't work either, for some reason it's not creating a
ssl.cert file in /mystic/data - I checked all the perms are ok which
they are, I think that's probably my issue, not that CL isn't actually working.
Well that didn't work either, for some reason it's not creating a ssl.cert file in /mystic/data - I checked all the perms are ok which they are, I think that's probably my issue, not that CL isn't actuall working.
Well I upgraded but still no joy, now I'm on the latest A49 from April
30 2023, and SSH is still broken for me :/
Will figure it soon.
Now that you're upgraded, try all of the things you were told to try before. ;)
Do you see an ssl.cert now?
If there's a write-up or how-to on the wiki, follow that and see if you can get it to work now that you're using the latest version.
Otherwise, I think I joined in on this conversation a bit late, what was the errors you were encountering?
No, still don't see it and it isn't creating it.
No, still don't see it and it isn't creating it.
Otherwise, I think I joined in on this conversation a bit late,
what was the errors you were encountering?
Never too late to the party, and thanks for your help and suggestions.
The wiki is always my first goto, once that fails me, I then ask
questions =)
You could try starting MIS through 'strace', to get a trace/log of what it's doing:
strace -f -vvv -s32768 /home/bbs/mystic/mis daemon 2>&1 | tee
/tmp/mis.log
Genius! This allowed me to find out the error, and fix it!
Yes, strace can come in handy when there seems to be no logical explanation to what's happening. I use it more and more often these
days. =)
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,043 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 109:33:32 |
| Calls: | 500,961 |
| Calls today: | 1 |
| Files: | 109,378 |
| D/L today: |
310 files (63,158K bytes) |
| Messages: | 304,913 |