Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNCHRONET    |    Rob Swindell fetishistic worship forum    |    43,341 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 43,298 of 43,341    |
|    Digital Man to Dumas Walker    |
|    Installing manually obtained let's encry    |
|    14 Feb 26 19:00:21    |
      TZUTC: -0800       MSGID: 55896.sync@1:103/705 2df7471d       REPLY: 74906.sync@723:320/1 2df72db8       PID: Synchronet 3.21b-Linux master/e1b6f4eca Feb 13 2026 GCC 12.2.0       TID: SBBSecho 3.37-Linux master/4e2f5eeaf Feb 13 2026 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       FORMAT: flowed       NOTE: FSEditor.js v1.105        Re: Installing manually obtained let's encrypt certificate        By: Dumas Walker to Digital Man on Sat Feb 14 2026 02:55 pm               > Since letsyncrypt isn't working here and the irc is down, I decided to        > figure out how to get the cert on my own.        >        > Let's Encrypt has a nice bit of software that installed easily and works        > just fine. I can apparently set it up with cron to run when I need it to.        > It created certificates without any issue. The problem now is that I cannot        > figure out where synchronet expects to find these certificates (aside from        > the self-signed one).              The filename and location is the same, whether it self-signed or signed by a       CA (e.g. letsyncrypt), it's ctrl/ssl.cert: https://wiki.synchro.       et/config:ssl.cert               > There is an entry about using something called certtool but that utility is        > old and appears broken so I hope that isn't the answer.        >        > ./jsexec certtool --import        > /etc/letsencrypt/live/capitolcityonline.net/fullchain.pem        >        > Throws a cryptlib error -43.              ../../3rdp_src/cl/cryptlib.h:#define CRYPT_ERROR_NOTFOUND ( -43 ) /*       Requested item not found in object */              Most likely, it just doesn't support the format of the .pem file.              I think the --import option expects a pkcs7 certificate, while       the --import-pkcs12 option expects a pkcs12 certificate.              The utility works for those that know how to work it.       --         digital man (rob)              Breaking Bad quote #25:       Now if I could only learn how to lick myself. - Hank Schrader       Norco, CA WX: 56.4øF, 81.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs       --- SBBSecho 3.37-Linux        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187       SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 700 840 860 880 226/30       SEEN-BY: 227/114 229/110 112 134 206 317 400 426 428 470 700 705 266/512       SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58       SEEN-BY: 633/280 712/848 902/26 5075/35       PATH: 103/705 218/700 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca