https://gitlab.synchro.net/main/sbbs/-/commit/e2e83629384d7540eda63a05
Modified Files:
exec/letsyncrypt.js
Log Message:
Remove nonsensical warning added in 89956b3d0c
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/d4bdf4ff5028e0c7709de1f0
Modified Files:
exec/letsyncrypt.js
Log Message:
Properly parse web hostname from sbbs.iniGet both the webroot and web hostname from sbbs.ini rather than usesystem.inet_addr. system.inet_addr is configured in the messagessection, so it's implied that it's for email addresses.Also, allow configuring the sysop email address with the SysopEmailglobal key in the ini file.This is a cleanup and duplicate of !82
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/00e0498cdaf72390e104d300
Modified Files:
exec/letsyncrypt.js
Log Message:
If the service host is changed, the old private key is invalid.Just delete the old private key and create a new one for the newhost.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/ba5462ba1e8444d8416bde8f
Modified Files:
exec/letsyncrypt.js
Log Message:
Insure the web RootDirectory ends in a slash.Reported by Compctech via DOVE-Net:"On a side note, I had to modify the letsyncrypt.js file to get letsencrypt towork. I had to add a / before .well-known on lines 86 - 89 & 96."I'm guessing this is because his sbbs.ini [Web] RootDirectory wasn't terminated with a slash.
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/b3492b803427dd5a202c1979
Modified Files:
exec/letsyncrypt.js
Log Message:
Recycle all servers/services after updating certificatePer Deon (ALTERANT) via DOVE-Net:Oct 7 09:47:16 d-11-1 synchronet: srvc 0060 BINKPS connection accepted from:2402:1f00:8101:b3c:1000::2 port 55338Oct 7 09:47:16 d-11-1 synchronet: srvc 0060 BINKPS TLS ERROR 'Servercertificate has expired' (-3) setting private keyOct 7 09:47:16 d-11-1 synchronet: srvc 0060 BINKPS TLS ERROR 'Data has notbeen initialised' (-11) setting session activeWhich was odd, because my cert was renewed.I forced renewed it, and confirmed it was valid, but they were still failing.I noticed that letsyncrypt only recycles the web, which is probably the issue.Once I recycled everything, binkps connections started working again.
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/38ca791314996ea325edd0e7
Modified Files:
exec/letsyncrypt.js
Log Message:
Use main.ini instead of main.cnf for system passwordFixes issue #471
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)