• src/sbbs3/rechocfg.c sbbs

    From Deuce@454:1/1 to Cvs Commit on Sun Apr 24 02:19:00 2016
    src/sbbs3 rechocfg.c 3.4 3.5 sbbsecho.h 3.3 3.4
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv17642

    Modified Files:
    rechocfg.c sbbsecho.h
    Log Message:
    free() old domain mappings before reading new ones.

    We can't pass a const char * to FREE_AND_NULL, so remove const qualifier
    rather than not use FREE_AND_NULL() here.



    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net
    þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)
  • From Deuce@454:1/1 to Cvs Commit on Sun Apr 24 02:19:00 2016
    src/sbbs3 rechocfg.c 3.5 3.6 sbbsecho.c 3.8 3.9 sbbsecho.h 3.4 3.5
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv18205

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Add support for an "OutgoingSemaphore" global INI value which, if set to a non-zero-length string, will touch/create that file if outgoing data has
    been processed.

    Intended to allow the mailer to scan as soon as outgoing data is available rather than having it wait for the next normally scheduled scan.

    Note, if using this feature as the *only* way to trigger a scan (not reccomended), any other sources of outgoing data (such as hatching files, interBBS doors, etc) will also need to touch this semaphore or they will
    not be sent until sbbsecho processes outgoing data.



    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net
    þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)
  • From Rswindell@454:1/1 to Cvs Commit on Sat May 28 10:16:00 2016
    src/sbbs3 rechocfg.c 3.9 3.10 sbbsecho.c 3.12 3.13 sbbsecho.h 3.5 3.6
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv9503

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Introduced sbbsecho.ini advanced setting (not yet exposed in echocfg): StrictPacketPasswords (default is "true").
    If you want SBBSecho v3 to behave like SBBSecho v2 with regards to packet passwords for linked-nodes with *no* configured packet password, set this value to "true" in your sbbsecho.ini file. I don't recommend doing this if you care about the "security" of your echomail, but some sysops have been bitten by the strict enforcement of the configured password in SBBSecho v3.

    I also fixed some (but not all) of the signed/unsigned value comparison warnings reported by msvc2013. Hopefully this didn't introduce any stupid bugs.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net
    þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)
  • From Bill Mcgarrity@454:1/1 to Rswindell on Sat May 28 10:16:00 2016
    Re: src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h
    By: rswindell to CVS commit on Mon May 09 2016 02:28:44

    Hiya Rob...

    Modified Files: rechocfg.c sbbsecho.c sbbsecho.h Log Message:
    Introduced sbbsecho.ini advanced setting (not yet exposed in
    echocfg): StrictPacketPasswords (default is "true"). If you want
    SBBSecho v3 to behave like SBBSecho v2 with regards to packet
    passwords for linked-nodes with *no* configured packet password, set
    this value to "true" in your sbbsecho.ini file. I don't recommend
    doing this if you care about the "security" of your echomail, but
    some sysops have been bitten by the strict enforcement of the
    configured password in SBBSecho v3.

    Just so I get this straight... if we want to accept the new feature in
    sbbsecho for strict pkt passwords protection then toggle this to "false". Correct??


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net:81
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: 6697
    Radio: radio.tequilamockingbirdonline.net:8010/live

    ... Look TWICE.... Save a life.... Motorcycles are EVERYWHERE!!

    ---
    þ Synchronet þ TequilaMockingbird Online - Toms River, NJ
    þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)
  • From Digital Man@454:1/1 to Bill Mcgarrity on Sat May 28 10:16:00 2016
    Re: src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h
    By: Bill McGarrity to rswindell on Mon May 09 2016 12:48 pm

    Re: src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h
    By: rswindell to CVS commit on Mon May 09 2016 02:28:44

    Hiya Rob...

    Modified Files: rechocfg.c sbbsecho.c sbbsecho.h Log Message: Introduced sbbsecho.ini advanced setting (not yet exposed in
    echocfg): StrictPacketPasswords (default is "true"). If you want SBBSecho v3 to behave like SBBSecho v2 with regards to packet
    passwords for linked-nodes with *no* configured packet password, set this value to "true" in your sbbsecho.ini file. I don't recommend
    doing this if you care about the "security" of your echomail, but
    some sysops have been bitten by the strict enforcement of the configured password in SBBSecho v3.

    Just so I get this straight... if we want to accept the new feature in sbbsecho for strict pkt passwords protection then toggle this to "false". Correct??

    No, strict is the default behavior of SBBSecho v3. It was the *only* behavior of SBBSecho v3 before this morning, but apparently there's some confused FidoNet sysops out there sending out password-protected packets and not realizing it. So this little option will allow you to use the old, less-secure, SBBSecho v2 method of password packet validation:

    If StrictPacketPasswords = true (the default), then the password in the packet must match whatever you (the receiving end) has configured in your sbbsecho.ini for the linked node. Just as it was in the initial SBBSecho v3 commits to CVS.

    If StrictPacketPasswords = false, then the password in the packet is only compared if the linked node has a password set in your (the receiving end's) sbbsecho.ini file. I don't recommend using this mode if you care about echomail security.

    digital man

    Synchronet "Real Fact" #34:
    The irc.synchro.net network has more servers than users.
    Norco, CA WX: 67.2øF, 62.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net
    i
    þ RNET 2.10U: ILink: Techware BBS þ Los Angeles, Ca þ www.techware.dynip.com

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)
  • From Rswindell@454:1/1 to Cvs Commit on Wed Jun 1 07:12:00 2016
    src/sbbs3 rechocfg.c 3.10 3.11 sbbsecho.c 3.13 3.14 sbbsecho.h 3.6 3.7
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv9290

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Sysop can over-ride the time-stamp format in the sbbsecho.log by setting
    the LogTimeFormat key in sbbsecho.ini. The default is "%Y-%m-%d %H:%M:%S".
    If you want the old (v2) time-stamp format, set this value to
    "%m/%d/%y %H:%M:%S". Any/all valid strftime() specifiers may be used.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net
    þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)