"4294967295 File closed"
"0000 File closed: /path/to/file"

If an incoming message contains no CHRS/CHARSET control line *and* the message
text contains valid UTF-8 character encodings, set the FTN charset value to
UTF-8 so the message will be displayed/handled accordingly.
I did not add checks for header fields (to/from/subject) - we should probably
auto-detect UTF-8 in those as well, but for now, I don't see messages coming
into FidoNet echoes with UTF-8 in the header fields.
Incremented SBBSecho/EchoCfg version to 3.10.

This only impacts the new socket_select() method with multiple arrays.

Instead, just return -1 from js_socket_recv().

Hopfully this doesn't break the Borland or Watcom (?!) builds.

it's a CP437 character (e.g. inadvertently included in a UTF-8 encoded text)
and display as such.

line too. The 0xFE (CP437 block) character is not a valid UTF-8 character
sequence.

function for external sockets.  However, service thrads that use TLS were
relying on the finalize function to clean up the TLS session.

Revert 1.242, and add a finalize parameter to do_js_close() which will only
avoid the shutdown() call rather than completely avoid do_js_close()
completely.

This fixes a TLS session leak that would eventually prevent any new
encrypted connections.

name. This is a fix for "From", but "To" and "CC" header fields would need
a similar fix (not included in this commit).

Reported by Rastus (EWBBS).

This should fix the crash in ircd.

We don't yet support UTF-8 in node/user messages.

It will return an object with properties corresponding to the passed
arrays, and the write parameter will be ignored.  This allows usage very
much like the select() syscall, and allows a traditional non-blocking
server to be written.

forever for 1 child thread (presumably the http_logging_thread) to terminate:

 >   8/27  02:39:43p  Waiting for HTTP logging thread to terminate...
 >   8/27  02:39:43p  HTTP logging thread started
 >   8/27  02:39:43p  HTTP logging thread received NULL linked list log entry
 >   8/27  02:40:44p  !TIMEOUT waiting for HTTP logging thread to terminate
 >   8/27  02:40:44p  Done waiting for HTTP logging thread to terminate
 >   8/27  02:40:44p  0000 Waiting for 1 child threads to terminate

 <infinite wait loop here>

- Add an extra terminate_http_logging_thread check to the top of the loop in
  http_logging_thread().
- Signal the log_list semaphore in the "Waiting for HTTP logging thread" and
  "Waiting for x child threads" loops.

scfg.prepped         = TRUE
scfg.tls_certificate = -1
scfg.sys_inetaddr    = "example.com"
scfg.sys_name        = "JSDoor"
scfg.sys_pass        = "ThisIsNotHowToDoSecurity"

The scfg_t instances are often shared between threads and we can't really share
file descriptors between threads, so we ended up with file descriptor leaks and
race conditions.

Instead, define/allocate/free a new js_system_private_t where the scfg_t* and
the nodefile (descriptor) are kept - per "system" instance.

subject header fields are non-ASCII yet valid UTF-8, set the auxattr flag
indicating that the msg header is in UTF-8.
This function is used by JS MsgBase.save_msg(), so any scripts/services that
use it (e.g. nntpservice, newslink, imapservice, etc.) to save messages with
header fields that may be UTF-8 encoded will automatically benefit from this
detection. Mixing CP437 (the default) with UTF-8 encoded header fields is not
supported, so if one header field is valid UTF-8 (not plain US-ASCII), then
they had better all be either plain US-ASCII or UTF-8 or there will be
UTF-8 decoding issues when attempting to display or convert later.

object/struct doesn't have any meaningful data. Prevent this from happening:
    SenderTime       19700101000000Z
    SenderIpAddr
    SenderHostName
    SenderPort       0

closeit parameter is TRUE

- If a telnet command was received in multiple packets, the memcpy optimization
  in telnet_interpret() would skip/drop all bytes in the subsequent pkt payload
  before an IAC char. Don't optimize when in the middle of a telnet command.
- If a received telnet command exceeds the telnet_cmd buffer, reset the
  received telnet_cmdlen and log a warning-level message
- If a telnet sub-negotiation END command is received as the beginning of a
  new telnet command, log a warning-level message and reset the telnet_cmdlen.

This fixes the occasional problem observed when using fTelnet and its sending
the "SEND-LOCATION" sub-neg command split between 2 TCP packets. Only
part of the first packet would be used as the location data and the rest
processed as input from the users (e.g. as the Login: prompt). Thanks, Ree!

Elminate unused member variable: inputfile

(ctrl/node.dab) is constantly closed and re-opened for every non-locking read.
This is really slow across network file systems and unnecessary, so use a
similar optimization as the C++ sbbs_t class where the file can (and normally
is) left open across multiple consecutive reads.

(ctrl/node.dab) is constantly closed and re-opened for every non-locking read.
This is really slow across network file systems and unnecessary, so use a
similar optimization as the C++ sbbs_t class where the file can (and normally
is) left open across multiple consecutive reads.
Create/use opennodedat() function.
Uses the new CLOSE_OPEN_FILE() macro from xpdev/filewrap.h.

the file and sets the descriptor to -1 (if not already < 0).

deprecation warning from MSVC.

https://patchwork.kernel.org/patch/9289177/