• src/sbbs3/rechocfg.c

    From Rswindell@454:1/1 to Cvs Commit on Mon Apr 18 12:00:00 2016
    src/sbbs3 rechocfg.c 3.0 3.1
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv14725

    Modified Files:
    rechocfg.c
    Log Message:
    Fix Area File (AREAS.BBS) parsing bug reported by Rob Starr:
    If one of the link addresses had a point specified (e.g. ".1") then all the addresses would get that point appended to them.
    Fixed atofaddr(): stop parsing the address at the *first* whitespace char.


    ---
    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 Tue Apr 19 10:51:00 2016
    src/sbbs3 rechocfg.c 3.1 3.2
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv4518

    Modified Files:
    rechocfg.c
    Log Message:
    Bug-fix: allow echocfg to set the [node:x] "route" key value.

    ---
    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 Sun Apr 24 02:19:00 2016
    src/sbbs3 rechocfg.c 3.6 3.7
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv31867

    Modified Files:
    rechocfg.c
    Log Message:
    Fix bug reported by Accession: couldn't save changes to NetMail->Default Recipient using echocfg.

    ---
    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.7 3.8
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv6915

    Modified Files:
    rechocfg.c
    Log Message:
    Fix reported crash when using SBBSEcho with FTN_Domains.ini support disabled. Don't free undefined variables.


    ---
    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 Sun May 1 10:45:00 2016
    src/sbbs3 rechocfg.c 3.8 3.9
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv28779

    Modified Files:
    rechocfg.c
    Log Message:
    Fix bug reported by Accession (Nick): Don't specify a default .ini key
    value (of "SYSOP") for the DefaultRecipient key. If it's blank (nobody)
    just leave it blank.


    ---
    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 Digital Man on Sat May 28 10:16:00 2016
    Digital Man wrote to Bill McGarrity <=-

    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.

    Thank you for the clarification. When I first read your explanation above it seemed it was reverse logic. I just wanted to make sure before I processed it.

    Thanks again...


    --

    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!!!
    --- MultiMail/Win32 v0.50
    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: Re: src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h
    By: Bill McGarrity to Digital Man on Tue May 10 2016 12:22 am

    Digital Man wrote to Bill McGarrity <=-

    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.

    Thank you for the clarification. When I first read your explanation above it seemed it was reverse logic. I just wanted to make sure before I processed it.

    Yes, I mistyped my CVS commit message. That should have said:

    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 "false" in your sbbsecho.ini file.

    I didn't catch that until just re-reading in your quoted text. Oops.

    digital man

    Synchronet "Real Fact" #60:
    How to get Synchronet technical support: http://wiki.synchro.net/howto:support Norco, CA WX: 55.3F, 87.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs ---
    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 Digital Man on Sat May 28 10:16:00 2016
    Digital Man wrote to Bill McGarrity <=-

    Re: Re: src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h
    By: Bill McGarrity to Digital Man on Tue May 10 2016 12:22 am

    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.

    Thank you for the clarification. When I first read your explanation above it seemed it was reverse logic. I just wanted to make sure before I processed it.

    Yes, I mistyped my CVS commit message. That should have said:

    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 "false" in your sbbsecho.ini file.

    I didn't catch that until just re-reading in your quoted text. Oops.

    Not a problem... those 2am postings can do that to ya.. I just wanted to make sure.. :)

    Thanks


    --

    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!!!
    --- MultiMail/Win32 v0.50
    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)