(executing echocfg.exe).

stack. Use the heap instead.

addresses configured in SCFG.
Added "Poll" sub-menu item to the Fidonet menu for convenient method of forcing
the BINKPOLL timed event to run.

- echocfg (executing)
- binkstats.ini (viewing)
- echostats.ini (viewing)
- sbbsecho.log (viewing)
- sbbsecho.ini (editing)
- badareas.lst (viewing)
- areas.bbs (editing)

I don't recall why I added this or what usefulness it has, but I'm gonna play
with it.

When importing an area list using the -import=<filename> option, if any
error occurred, scfg would segfault while trying to display the error
message because it was trying to use uifc.msg() which was a NULL pointer.

ie: Does not return if the path was made or not.

to before the actual export, so that if an area has no downlinks, you won't
actually see this errorneous but harmless log message. Also include the
"export-to" address in the message.

mutexes are undefined in children.

it before redirecting stdout to the pipe.

Likely fixes CGI errors seen by alterego (and has been broken for almost
fifteen years).

Avoid gratuitous xim reallocations (not a bug)
Avoid gratuitous redraws (not a bug)
Avoid posting and waiting on a semaphore from the same thread (ehhhh....)
After blocking on XNextEvent(), drain all X events in the queue (not a bug)

Also not an issue.

This didn't cause problems, but it was confusing.

passed.

Fixed but I think DigitalMan reported where the count of entries isn't
updated after and add/delete until you change to the settings menu and back.

If this option is set, it means that all content available via http:// is
available at the same https:// URL.  This will trigger to new behaviours:
1) If an HTTP request has the "Upgrade-Insecure-Requests: 1" header, the
   client will get a 307 redirect to the https:// URL.
2) For https:// responses, the following two headers will be added:
   Content-Security-Policy: block-all-mixed-content
   Strict-Transport-Security: max-age=10886400; preload

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fb3be8ce071 in do_cgi_stuff (session=0x7fb2fbfaac40, cgi=0x7fb2fbfaa850, orig_keep=1) at websrvr.c:4376
4376                                                            SKIP_WHITESPACE(value);

is Custom, and you modify the custom mode.

This uses global pointers to automatic variables... and other insane things.

now accept an optional print-mode (a.k.a. pmode) argument to provide more
control over the printing that happens in these functions/methods.
The immediate use is for P_NOCRLF to stop the newline from being printed
after a yes or no response (e.g. in a full-screen UI), but there could be other
uses.

Could sear I'd already done this.

checking for non-NULL value.

to an object with JSVAL_TO_OBJECT(). Go figure.

JS) which will be executed when a users uses the the (L)ist msgs command from
the "Reading" sub or "Reading E-mail" prompt.
The arguments passed to the module are: <sub-code> [which]  [usernum]  [lm_mode]
The additional optional arguments are the same values as would be passed to a
readmail_mod, if one were to be used instead.

src\sbbs3\js_global.c(3703): warning C4018: '<': signed/unsigned mismatch
src\sbbs3\js_global.c(3761): warning C4018: '<': signed/unsigned mismatch
src\sbbs3\js_global.c(3779): warning C4018: '<': signed/unsigned mismatch

MsgBase.get_msg_header or get_all_msg_headers), the message header object's
private data (used internally in these C source functions) would be freed and
NULL'd, apparenty as a form of optimization. This would cause some methods
which can accept a msg header object as an argument (e.g.
MsgBase.put_msg_header, bbs.show_msg/show_msg_header) to fail or behave
in strange ways.

Instead of freeing/NULLing the private data (and depending on that as an
indication that the header has been enuemrated), just set a member variable
indicating that the header has been enumerated (once) already.

This is the bug that has been tripping me up with my message lister JS mod
(see YouTube video). I can finally get that committed to CVS for testing now.
:-)

As reported by Ragnarok (DOCKSUD)

(said port 0) since the port had not been bound yet.
So fix the display order of that msg (after listen() is called)
and lower the log level to debug.

We don't need PCI DSS compliance I hope, we just want people doing things.

only (you can still use them from JS etc).