As Nelgin pointed out, mouse hot-spots were still active when running external
programs (door games) - so clear any active hot-spots before running external
programs.

This could possibly be done in external() instead, but this sufficient for
now. I wouldn't want a menu that EXEC's something (via @-code) to lose all its
hot-spots as a result.

This is for sysops that never want mouse hot-spots in their BBS menus and
prompts (e.g. Kirkman, possibly Deuce) - set to "No".

Setting to "No" also disables the function of the JS console.add_hotspot()
method. Perhaps it should not. <shrug>

Setting to "No" does not disable the terminal mouse support question when
users are setting their terminal defaults. Perhaps it should.

This option should default to enabled (sysops that depend on mouse hot-spots
should double check) - it's enabled in new/stock installs.

Because the session is activated on the *next* time through the
loop, if the third attempt to authenticate (including public key)
fails, it would leave the session inactive and fail to log in with
a confusing error about an obsolete cryptlib.

On success, decrement ssh_failed to ensure another pass through
the loop.

Also, add more debug logging around the auth so you can clearly
see each failure, and log client_socket each time so it's clearly
grouped.

... declutter a bit more of the menus.

Also added the new option to disable HTTP support in the web server.

And center the sub-menus.

Allow SFTP support to be enabled/configured in SCFG->Servers and
SBBSCTRL->Terminal->Configure.

SFTP session inactivity applies to 'H' exempt users too (intentionally).

And use it in the open() args log.

This explains the extra calls to record_transfer() on Windows SFTP server

I do wonder if we should be usign sopen() or nopen() here instead though.

This makes the Terminal Server settings menu a bit less cluttered. And now
we can add more SSH settings (like SFTP, Any Auth).

Q for Deuce: record_transfer() is being called multiple times for non-filebase
file transfers, resulting in duplicate log messages. This doesn't happen for
filebase file transfer (downloads, anyway).

For SFTP sessions, there's no shell/terminal, so no need to run command
shells (with their input timeouts, etc.). Reflect the node connection as
"via sftp" in the node status. Handle node interruption signal. Probably more
to do here with node status/actions (e.g. it'd be nice to set the action to
"uploading or "downloading" when appropriate).

These functions take a uint32_t, not a time32_t (which is an int32_t).

Every SFTP login/off would reset the user's new-file-scan date to Jan-1-1970

To support the full 32-bit range for things like dates/times, and message
numbers (!).

This should fix issue #732

Though dates beyond Feb 7 2106 are definitely going to still be an issue. I'll
definitley look into solving that by the the 2100.

See sbbs_t::logon() for example

Note: the client.protocol is still "SSH" here (not "SFTP"). Perhaps that
should be changed?

Does any client actually support simultaneous "SSH" and "SFTP" sessions over
the same socket?

Found by Coverity.

The array overrun crashed Win32, the asprintf() usage imacts glibc
and the other warnings are impossible (an exception would have been
thrown).

This includes the "OK" error, and numerous other normal errors,
so most of them are logged as LOG_DEBUG.

Also fail early if parsing underruns root.

This Win32 function behaves differently on Win32 than *nix, and
does not do what we want.

Instead, copy the important bits from xpdev, and resolve a TODO.

Oops, missed this with the cl32.dll commit.