• src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h

    From deuce@VERT to CVS commit on Wed Apr 20 23:24:32 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
  • From rswindell@VERT to CVS commit on Mon May 9 06:28:44 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
  • From Bill McGarrity@VERT/TEQUILAM to rswindell on Mon May 9 16:48:08 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
  • From Digital Man@VERT to Bill McGarrity on Mon May 9 22:32:01 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
  • From Bill McGarrity@VERT/TEQUILAM to Digital Man on Tue May 10 04:22: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
  • From Digital Man@VERT to Bill McGarrity on Tue May 10 04:59:36 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.3°F, 87.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From Bill McGarrity@VERT/TEQUILAM to Digital Man on Tue May 10 14:21: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
  • From rswindell@VERT to CVS commit on Mon May 30 23:01:55 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
  • From rswindell@VERT to CVS commit on Wed Aug 3 04:24:44 2016
    src/sbbs3 rechocfg.c 3.11 3.12 sbbsecho.c 3.17 3.18 sbbsecho.h 3.7 3.8
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv3013

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    SBBSecho will now (by default) *not* forward filtered messages to downlinks. Filtered messages include messages not imported due to age, twitlist, dupes, etc. To change this behavior, set RelayFilteredMsgs=true in your sbbsecho.ini.


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From Wilfred van Velzen@VERT to rswindell on Wed Aug 3 15:11:52 2016
    Hi rswindell,

    On 2016-08-03 00:24:44, you wrote to CVS commit:

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    SBBSecho will now (by default) *not* forward filtered messages to downlinks. Filtered messages include messages not imported due to age, twitlist, dupes, etc. To change this behavior, set RelayFilteredMsgs=true in your sbbsecho.ini.

    You should differentiate between technical issues: age and dupes. And political
    issues: Twitlist. Because the latter would make synchronet censor a feed according to the private opinion of the sysop.

    Bye, Wilfred.

    --- FMail-W32 1.69.22.178-B20160706
    * Origin: FMail development HQ (2:280/464)
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From Digital Man@VERT to Wilfred van Velzen on Wed Aug 3 12:17:10 2016
    Re: Re: src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h
    By: Wilfred van Velzen to rswindell on Wed Aug 03 2016 11:11 am

    Hi rswindell,

    On 2016-08-03 00:24:44, you wrote to CVS commit:

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    SBBSecho will now (by default) *not* forward filtered messages to downlinks. Filtered messages include messages not imported due to age, twitlist, dupes, etc. To change this behavior, set RelayFilteredMsgs=true in your sbbsecho.ini.

    You should differentiate between technical issues: age and dupes. And political
    issues: Twitlist. Because the latter would make synchronet censor a feed according to the private opinion of the sysop.

    That's an idea. Technically, it wouldn't be Synchronet censoring anything, but SBBSecho, but I get your point.

    Also, I mispoke (again): filtered dupes are not subject to this new setting: they're never forwarded to downlinks.

    digital man

    Synchronet "Real Fact" #59:
    Synchronet apparel and merchandise can be purchased at cafepress.com/synchronet Norco, CA WX: 71.4°F, 78.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From Wilfred van Velzen@VERT to Digital Man on Wed Aug 3 21:55:20 2016
    Hi,

    On 2016-08-03 08:17:10, Digital Man wrote to Wilfred van Velzen:
    about: "Re: src/sbbs3/rechocfg.c sbbsecho.c sbbsecho.h":

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    SBBSecho will now (by default) *not* forward filtered messages to
    downlinks. Filtered messages include messages not imported due to
    age,
    twitlist, dupes, etc. To change this behavior, set
    RelayFilteredMsgs=true in your sbbsecho.ini.

    You should differentiate between technical issues: age and dupes. And
    political
    issues: Twitlist. Because the latter would make synchronet censor a feed
    according to the private opinion of the sysop.

    That's an idea. Technically, it wouldn't be Synchronet censoring anything, but SBBSecho, but I get your point.

    For me Synchronet == SBBSecho ;)

    Also, I mispoke (again): filtered dupes are not subject to this new setting: they're never forwarded to downlinks.

    That's good!

    Bye, Wilfred.


    --- FMail-W32 1.69.22.178-B20160706
    * Origin: Native IPv6 connectable node (2:280/464)
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From rswindell@VERT to CVS commit on Sat Oct 28 17:15:22 2017
    src/sbbs3 rechocfg.c 3.21 3.22 sbbsecho.c 3.44 3.45 sbbsecho.h 3.17 3.18
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv16838

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    EchoStats filename (data/echostats.ini) is now configurable.
    EchoStats now contain message timezones (when written) and a "known" flag
    (bad echoes have known = false).
    EchoStats are now sorted before being written to the EchoStats file.
    Fixed bug in getfmsg(): trailing ex-ASCII chars of the message body would be chopped-off - go back to using a uchar.
    Re-worked packed-msg import parsing and grunged message detection a bit to
    log more msg details for all EchoStats.
    Added "AutoAddSubs" feature (set to true in sbbsecho.ini to enable):
    - If sub-boards are created (e.g. with SCFG) in one or more message groups, the
    areas can be automatically added to your Area File (areas.bbs)
    - The hub must be first configured in EchoCfg->Linked Nodes and then you set
    the GroupHub key in sbbsecho.ini to the name of the message group that this
    link is the hub for (e.g. "FidoNet"). You can specify multiple groups, if
    necessary, by comma-separating the names.



    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Fri Apr 3 19:20:24 2020
    src/sbbs3 rechocfg.c 3.44 3.45 sbbsecho.c 3.155 3.156 sbbsecho.h 3.38 3.39 Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv29309

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Use a .ini style (for sbbsecho.ini) more compatible crudini/python-iniparse
    - don't indent keys
    - separate sections with a blank line (to improve readability without idents)

    A nice tip from Ragnarok (DOCKSUD)!


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Ragnarok@VERT/DOCKSUD to rswindell on Mon Apr 6 04:38:47 2020
    El 3/4/20 a las 19:20, rswindell escribió:
    src/sbbs3 rechocfg.c 3.44 3.45 sbbsecho.c 3.155 3.156 sbbsecho.h 3.38 3.39 Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv29309

    Modified Files:
    rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Use a .ini style (for sbbsecho.ini) more compatible crudini/python-iniparse
    - don't indent keys
    - separate sections with a blank line (to improve readability without idents)

    A nice tip from Ragnarok (DOCKSUD)!

    ---
    � Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net

    cool, thanks!

    ---
    ■ Synchronet ■ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar