It is almost 2024 after all. :-)

Every server should have *some* limit to protect against DOS attacks.
Every connected client consumes a socket, a thread, some memory, none of
which are infinite resources.

... unless the full path was specified.

Also, expand the lock in websrvr to the correct scope.

May help nail down issue with keys.

We'll hold a reader lock under the session is established, which
should prevent blocking other threads unless something is beating
on get_ssl_cert() (which would be a different bug).

This still needs to be figured out, but at least this should fix
the immediate issue.

Remove some redundant redundancies, redundantly

it's only called from load_cfg() which has already set it to -1.

We also don't need to check prepped twice to make sure it's extra true.

Ctrl-A in the Failed Logins dialog now selects-all rather than copy-all (just
use Ctrl-A, then Ctrl-C to copy all).

warning: result of comparison of constant 100000 with expression of type 'uint16_t'
(aka 'unsigned short') is always true

./scfg.h:80:9: warning: 'SUB_HDRMOD' macro redefined [-Wmacro-redefined]

This is always going to call the terminal server's lprintf function (when used
with libsbbs.so/sbbs.dll) which is probably not what was intended.

Resolve reported clang warning:

inkey.cpp:592:20: warning: implicit conversion from 'long' to 'int' changes value from 2147483648 to -2147483648 [-Wconstant-conversion]
         if(!term_supports(MOUSE))
             ~~~~~~~~~~~~~ ^~~~~
 ./sbbsdefs.h:574:19: note: expanded from macro 'MOUSE'
 #define MOUSE           (1L<<31)                /* Mouse supported terminal                             */

This is hacky cruft here. We shouldn't have the declaration in multiple
places. It probably shouldn't be in sbbs.h.

load_cfg() calls free_cfg() before do_cryptInit() is called, so the ssl_rwlock
was uninitialized here.

Holding the lock around session establishment should not be needed,
but we need to protect tls_certificate read and usage.  Since we
don't have rwlocks in xpdev (yet?), hack together a crappy rwlock
that does what we need.

Also, remove "CONSECUTIVE", which doesn't really make sense when the number
of login attempts in 1.

There's a hidden checkbox on the CodeInputForm now (explaining why the edit/
combo box is now moved up).

Renamed the "Perm Filter Threshold" to "Auto Filter Threshold".

Changed help text from "Permanent" to "Persistent"

More readable/friendly log messages and ip.can reason strings

The number of failed login attempts. It's something.

Update wording and add more help text.

Now a sysop can "perm block" a client (IP address) for a limited amount of
time rather than always forever.

Add more displays of the ip.can details when actively blocking a client.

Moved twit/trash functions from userdat.c to trash.c

For symmetry