Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 48051  |
|  Deucе to Git commit to main/sbbs/master  |
|  src/doors/clans-src/src/myopen.c  |
|  07 Nov 25 21:34:07  |
 TZUTC: -0800 MSGID: 53465.syncprog@1:103/705 2d74dd28 PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 TID: SBBSecho 3.31-Linux master/d39e01091 Nov 03 2025 GCC 12.2.0 BBSID: VERT CHRS: UTF-8 4 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/commit/9348800631343e81cc11b0a5 Modified Files: src/doors/clans-src/src/myopen.c Log Message: Decrypt the buffer after writing In the majority of cases, buffers written to disk are not used again, however, when updating the scores as part of the BBS 1 maintenance, the current date would get written to the ipscores.dat file from the global. Since EncryptWrite() would now leave it encrypted, when the date was then copied into a users clan record, it was garbage. Just in case something like this happens anywhere else, ensure the buffer is unencrypted when EncryptWrite() returns. Introduced in d1693a60 --- SBBSecho 3.31-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 |
[ << oldest | < older | list | newer > | newest >> ]