Unable to set key (-2)
Based on the error it's something with the encryption key, so I am not sure where to start looking or what it could be. I installed Libcrypt successfully, but maybe somehting is off? I'm not sure. ANyone seen this error or have any thoughts?
--- Mystic BBS v1.12 A47 2021/04/08 (Raspberry Pi/32)
I believe the key is located at mystic/data/ssl.cert:
pi@bbs:~/mystic/data $ ll ssl.cert
-rw------- 1 pi pi 1.8K May 28 09:30 ssl.cert
pi@bbs:~/mystic/data $ stat -c "%a %n" ssl.cert
600 ssl.cert
Make sure the permissions are set correctly, adjust if necessary:
chmod 600 ssl.cert
I'm unsure how to regenerate the file though if you can't restore it from backup. I know Mystic generated mine, just not sure how/when.
Thank you. Hopefully someone will have more knowledge then both of us
and be able to share.
You can also post to the Fidonet MYSTIC echo. g00r00 who is the author
of Mystic hangs out there and would probably know the answer to this.
OK, I'll hop on a BBS with Fido and do that.
I believe the key is located at mystic/data/ssl.cert:
I'm unsure how to regenerate the file though if you can't restore it
from backup. I know Mystic generated mine, just not sure how/when.
I understand if you delete this then restart Mystic server it will regen the key.
Yes Paul, that is correct.
And for future reference, g00r00 was able to diagnose the issue. I installed the beat which didn't work with Mystic. So I just grabbed 3.43 as it says on the wiki that is known to work.
So I did a sudo make clean and recompiled 3.43. Fired the BBS back up
and it connected no problem. I'm back to 100% on the BBS.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 95 |
Nodes: | 16 (0 / 16) |
Uptime: | 01:49:32 |
Calls: | 4,624 |
Files: | 8,491 |
Messages: | 348,757 |