saving changes.

Nov-28-2017 (don't save .ini files with every change of log-levels), it was
quite easy for the visible log level controls and the actual log level (in the
startup structures) to get out-of-sync.

I'm pondering saving the selected log-level when recycling or something else,
but for now at least the visible controls match the real log level.

recursive make of scfg, uedit, and umonitor.

Also, free() temp variables for RSA keys.

of the passed filei, fixing a long-standing issue with a couple of menu
commands (e.g. "MAININFO") in the WWIV (and possibly other) command shells.
Thank Nelgin. Are we keeping count yet?

creates/deletes the file: ctrl/sysavail.chat

so they can be more easily used by external utils (e.g. umonitor).

This allows disabling authentication after a higher level specifies an
AccessRequirements value, eliminating the last reason to keep access.ars
around.

Also, allow signing unrecognized attributes.

These changes allow getting a Let's Encrypt certificate covering multiple
domain names.

attribute_get/set[_string|_time]? interface.  This is way easier than a
bunch of tiny getter/setter functions, and most of these certificate
extensions aren't actually going to be used anyway.

Also, surface the attribte cursor constants for more advanced certificate
parsing/creation.

time.

the default/all target.
So a single "make" command in src/sbbs3 should build these nested targets
as well.
Caveat: "make clean" does not clean these sub-make targets.

uedit.c:1475:5: warning: this 'if' clause does not guard...
     if(uifc.changes)

but it's parsed as a number.  Use the JS Date type for the values.

we are always freeing the pointer that was asigned the text.dat list and things
will crash (thanks for the report, Rastus).

Also add add_public_key() and get_public_key() methods to CryptKeyset.
Not tested yet, but this should be everything we need to finish up
LetSyncrypt.

This class allows saving and loading private keys.  It doesn't currently
allow saving or loading *public* keys, since they require certificate support
which we don't yet have in our JavaScript Object Model.

I'll fix the JSDocs build in a minute.

L (capital 'L'): Lock a message base
U (capital 'U'): Unlock a message base

These commands maybe used to insure that a message base is not modified while
being backed-up (but don't forget to unlock them when you're done!).

Also note: if you back up all the files (including *.lock), then the backed-up
message bases will also be locked and will need to be unlocked (i.e. *.lock
removed) before they may be used again if/when restored.

allow the "last_msg" value to be changed as well.
When dumping a msgbase index, show 'M' for messages (not blank).
When running maintenance, read the entire index in one shot.
Don't display progress (percentage counting) during maintenance (just
slows it down).
When reading messages, get the plain-text version (MIME decode if needed).
When a message base fails to open, continue processing additional message bases
if specified on the command-line.