TZUTC: -0800   
   MSGID: 51623.syncprog@1:103/705 2c063320   
   PID: Synchronet 3.20c-Linux master/a8d818585 Jan 28 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/a13f6c326 Feb 02 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: UTF-8 4   
   https://gitlab.synchro.net/main/sbbs/-/commit/94a109ca3acb0db20f314926   
   Modified Files:   
   	exec/broker.js   
   Log Message:   
   Support uid/pw only auth   
      
   There are now two ways to authenticate with the broker:   
   1) TLS PSK with a sysop account, and set the password field at the   
      MQTT level to the system password (user field, if present is   
      ignored).  This is the prefered method as it provides mutual   
      authentication and you simply can't steal credentials with MITM.   
   2) Synchronet TLS certificate, sysop username and the users password   
      followed by a colon, followed by the system password.  The server   
      authentication will now depend on the appropriate trust chain in   
      the client.  If using a Let's Encrypt certificate for example,   
      you can' securely connect to localhost with this method.   
      
   tools and libraries tend to allow TLS-PSK with password at the MQTT   
   level, many GUI tools do not allow TLS-PSK.   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426