TZUTC: -0700   
   MSGID: 52791.syncprog@1:103/705 2d48863b   
   PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: UTF-8 4   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/22c72fd3c7505f04936a43d7   
   Modified Files:   
   	src/syncterm/bbslist.c syncterm.c syncterm.h   
   Log Message:   
   Allow the system list path to be an http:// or https:// URL   
      
   As per feature request 86, now you can put an encrypted BBS list   
   on the web somewhere and use it from anywhere.   
      
   I expect how this would normally be used is that your "main" system   
   would have a static IP and a web server on it, and you would set the   
   BBS list path there to be somewhere in your web root, and encrypt   
   your SyncTERM list with a hard to guess and unique password.   
      
   Then, on other systems, you would just point it there.   
      
   This does allow someone to do an offline attack against your list   
   password and if they crack it, they'll get all your passwords from   
   when they downloaded your list, so not exactly perfect security, but   
   considerably better than nothing... and if we end up needing post-   
   quantum cryptography you'll need to rotate all of your passwords.   
      
   Another alternative of course is to use SSH public key auth and not   
   store passwords in the file at all, but you'll still want to store   
   them somewhere...   
   --- SBBSecho 3.30-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: 129/14 153/7715 154/110 214/22 218/0 1 215 610 700 810 226/30   
   SEEN-BY: 227/114 229/110 206 317 400 426 428 470 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