Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 48352  |
|  Deucе to Git commit to main/sbbs/master  |
|  src/sbbs3/answer.cpp  |
|  19 Dec 25 11:28:55  |
 TZUTC: -0800 MSGID: 53778.syncprog@1:103/705 2dabaf89 PID: Synchronet 3.21a-Linux master/48922a15c Dec 17 2025 GCC 12.2.0 TID: SBBSecho 3.33-Linux master/48922a15c Dec 17 2025 GCC 12.2.0 BBSID: VERT CHRS: UTF-8 4 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/commit/114c3dfdee48db651bf568fa Modified Files: src/sbbs3/answer.cpp Log Message: Fix potential deadlock in specific case If the telnet client sends an IP address as a Location, and that IP address is in a filter file, the input thread mutex would not be unlocked. This oddball feature was suggested on Reddit here: https://www.reddit.com/r/synchronet/comments/khuyey/ftelnetwebsocketservicejs/ And implemented in Synchronet here: https://gitlab.synchro.net/main/sbbs/-/commit/2bbe824c0656176d03 4f2d48558b322a69b9e32 It appears that it's been broken the whole time. Found by some LLM (ChatGPT?) and reported by nelgin. --- SBBSecho 3.33-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 10/0 1 102/401 103/705 105/81 106/201 124/5016 128/187 129/14 SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 700 810 226/30 227/114 SEEN-BY: 229/110 134 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 >> ]