https://gitlab.synchro.net/main/sbbs/-/commit/cc717b4025d6193db3004937
Modified Files:
src/sbbs3/scfg/scfgsys.c src/sbbs3/scfgdefs.h scfglib1.c scfgsave.c ssl.c
Log Message:
Add/use option: SCFG->System->Security->Create Self-signed Certificate

Default to false / No. Maybe this should default to true / Yes until a certificate (e.g. from Let's Encrypt) is successfully provisioned?

Anyway, this is just a quick-hack to address the issue where a sysop's CA-sigend certificate may be overwritten with a self-signed certificate if
for some reason Synchronet can't find/read the ssl.cert file.

See issue #881.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/85dea26141fc2f9fd9033a71
Modified Files:
src/sbbs3/scfg/scfgsys.c src/sbbs3/scfgdefs.h scfglib1.c scfgsave.c userdat.c
Log Message:
Make the "high quality" password checking optional (default: off/false)

To enable high quality/entropy password checking, set SCFG->System->Security ->Demand High Quality Password to "Yes".

This defaults to false since the "quality" standard is higher than it used to be and that could be confusing for sysops or users.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net