Subj : exec/load/logonlist_lib.js exec/logonlist.js
To   : Git commit to main/sbbs/master
From : Rob Swindell (on Debian Linux)
Date : Sun Jun 09 2024 18:52:09

https://gitlab.synchro.net/main/sbbs/-/commit/16c5298fa047acd7051ccece
Modified Files:
	exec/load/logonlist_lib.js exec/logonlist.js
Log Message:
Log the current connection protocol as a separate property in logon.jsonl

Accession reported that (sometimes?) his NNTP logins show up in his
logon.jsonl files. This is most likely just a race condition when logging
in close to the same time with multiple protocols (e.g. Telnet and NNTP
in this case). So, let's log the client.protocol as a separate JSON property
and not require on the user.connection property (which is overwritten for
*every* login, for almost all connection/server types, not just the terminal
server). The client.protocol is always correct for the current session running
the script.

An NNTP login should never appear in the logon.json file.
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.