TZUTC: -0800   
   MSGID: 51968.syncprog@1:103/705 2c33282c   
   PID: Synchronet 3.20e-Linux master/7c30785d2 Mar 05 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/2adf8468d Mar 06 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   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.   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 700 810 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 550 700 705 266/512 280/464   
   SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426