• Re: Bugs Report (4/13/16)

    From Bill McGarrity@1:266/404 to Lord Time on Fri Apr 15 17:25:00 2016
    Lord Time wrote to Digital Man <=-
    ok, I didn't look at it to closely

    you will find a file called problem.zip it has my areas.bbs & sbbsecho.cfg & sbbsecho.cfg & sbbsecho.log, if you want the files (before the toss) let me know and I'll zip them up (made backup - didn't want to re-name them again)

    With the fixed log output, the problem is now obvious: it's appending a ".1" point to the parsed addresses. It's an easy fix I'm about to commit.

    ok and good :)

    still a small problem, sending over sbbsecho.log (note this is with sbbsecho_upgrade.js 1.10)

    I'm not sure if this could be an issue with the way it upgraded you but you started sending over PKT's that were password pprotected and I had a bunch here that were bad from you. I added our session lvel password in echocfg, renamed the PKTs and poof, it worked...

    I don't mind leaving the PKT password if that's what you want.

    Enjoy!!




    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Lord Time on Sat Apr 16 09:54:00 2016
    Lord Time wrote to Bill McGarrity <=-

    Lord Time wrote to Digital Man <=-
    ok, I didn't look at it to closely

    you will find a file called problem.zip it has my areas.bbs & sbbsecho.cfg & sbbsecho.cfg & sbbsecho.log, if you want the files (before the toss) let me know and I'll zip them up (made backup - didn't want to re-name them again)

    With the fixed log output, the problem is now obvious: it's appending a ".1" point to the parsed addresses. It's an easy fix I'm about to commit.

    ok and good :)

    still a small problem, sending over sbbsecho.log (note this is with sbbsecho_upgrade.js 1.10)

    I'm not sure if this could be an issue with the way it upgraded you but you started sending over PKT's that were password pprotected and I had a bunch here that were bad from you. I added our session lvel password in echocfg, renamed the PKTs and poof, it worked...

    was the first time around 4/13/16 for about 2 hr. and yesterday
    (4/14/16) for a few mins, and today (4/15/16) for a few mins, if it
    was, it was the the new sbbsecho stuff

    Things happen... I'm easy... just go with the flow. :) I look at things in the KISS format. Usually it's something so easy to fix yet we tend to look for the impossible. Took me about 5 minutes to figure out it was pky passwords..

    I don't mind leaving the PKT password if that's what you want.

    yep, I have the packet & message part set with a pw. for you


    OK... :)


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Lord Time on Sat Apr 16 18:26:00 2016
    Things happen... I'm easy... just go with the flow. :)


    I look at things in
    the KISS format. Usually it's something so easy to fix yet we tend to look for the impossible. Took me about 5 minutes to figure out it was pky passwords..

    good, are you sure that sbbsecho or the cfg file took it out?

    We never had a PKT password, only session level. That's why I was surprised when I saw the BAD pkts. When I opened the BAD pkts up I saw you had added the PKT password somehow.



    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Lord Time on Sun Apr 17 11:14:00 2016
    Lord Time wrote to Bill McGarrity <=-

    Things happen... I'm easy... just go with the flow. :)

    I look at things in
    the KISS format. Usually it's something so easy to fix yet we tend to look for the impossible. Took me about 5 minutes to figure out it was pky passwords..

    good, are you sure that sbbsecho or the cfg file took it out?

    We never had a PKT password, only session level.

    hmmm, I've have them in from day one even netmail to you, before I
    figure out how you did your echo's on your net, I even did a %recan
    with pw and had no problems

    That's why I was surprised when I saw the BAD pkts. When I opened the
    BAD pkts up I saw you had added the PKT password somehow.

    look like sbbsecho took them out on your side


    I never had PKT passwords for Whispnet and I don't have them for you on Sportnet. Are you getting bad pkt's from me in z24?


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Lord Time on Sun Apr 17 17:39:00 2016
    Lord Time wrote to Bill McGarrity <=-

    Things happen... I'm easy... just go with the flow. :)

    I look at things in
    the KISS format. Usually it's something so easy to fix yet we tend to look for the impossible. Took me about 5 minutes to figure out it was pky passwords..

    good, are you sure that sbbsecho or the cfg file took it out?

    We never had a PKT password, only session level.

    hmmm, I've have them in from day one even netmail to you, before I figure out how you did your echo's on your net, I even did a %recan with pw and had no problems

    That's why I was surprised when I saw the BAD pkts. When I opened the BAD pkts up I saw you had added the PKT password somehow.

    look like sbbsecho took them out on your side

    I never had PKT passwords for Whispnet and I don't have them for you on Sportnet. Are you getting bad pkt's from me in z24?

    yep, so I'em not on v3.00 of sbbsecho, I'll send you a netmail


    OK...


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Allen Prunty on Mon Apr 18 08:31:00 2016
    Allen Prunty wrote to Bill McGarrity <=-


    I wonder what the benefit of PKT passwords are? Never used them even
    back in the day.

    They have their need. It was to prevent mail bombs back in the old days with POTS.


    Also what is the best internet front door style mailer for Synchro?
    I'm surprised that it's not built in by now :-)

    I use Binkd right now but DM, Deuce and eChicken are working on BinkIt which is a built-in mailer for V4.0 if I can remember correctly.




    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to echicken on Mon Apr 18 18:42:00 2016
    echicken wrote to Bill McGarrity <=-

    I use Binkd right now but DM, Deuce and eChicken are working on BinkIt which is a built-in mailer for V4.0 if I can remember correctly.

    IIRC most if not all of the recent binkp-related work has been done by Deuce. I haven't contributed to it.

    Maybe no, but you're an important contributor to other things that add to a successful package... :)


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Digital Man on Wed Apr 20 10:03:00 2016
    Hiya Rob...

    Digital Man wrote to Lord Time <=-

    Re: Re: Bugs Report (4/13/16)
    By: Lord Time to Digital Man on Tue Apr 19 2016 05:42 pm

    ok, now running 4/19/16 build of sbbsecho & echocfg.exe & sbbsecho_upgrade.js
    I notice a few things, it look like if your getting message packs from bbbs bbs software, it don't see the packet pw

    from 1:261/38

    2016-04-19 14:04:21 Unpacking bundle: d:\sbbs\taurus\inbox\secure\dd8e7da2.tu1 (10.1KB)
    2016-04-19 14:04:21 Packet d:\sbbs\taurus\inbox\secure\dd8e7d1d.pkt from 1:261/38 - Incorrect password ('' instead of '*********')

    Can you use pktdump to view the packet header and paste the output here or send the packet to me for inspection?

    also some game pack :

    any league 10 message pkt

    2016-04-19 14:04:21 Packet d:\sbbs\taurus\inbox\secure\5769025e.pkt from 10:10/161 - Incorrect password ('' instead of '*********')

    <ditto>

    will send a copy of both over to you, when the next one on each get here

    Same thing for the packet you just sent (no password):

    # pktdump 578096C4.PKT
    pktdump rev 1.8 - Dump FidoNet Packets

    Opening 578096C4.PKT
    578096C4.PKT Packet Type 2.0 (prod: 00, serial: 0) from 10:10/161 to 10:10/1 0000003A
    578096C4.PKT 00003A Packed Message Type: 2 from 10/161 to 10/1
    Attribute: 0191
    Date/Time: 19 Apr 16 18:57:53
    To : BRE System
    From : BRE System
    Subj : ^E:\SBBS\DOORS\INTERBBS\010\BRE\OUTBOUND\010B0601.223
    00000100
    578096C4.PKT 000100 Packed Message Type: 2 from 10/161 to 10/1
    Attribute: 0191
    Date/Time: 19 Apr 16 18:57:54
    To : FE System
    From : FE System
    Subj : ^E:\SBBS\DOORS\INTERBBS\010\FE\OUTBOUND\010F0601.188
    000001C3
    578096C4.PKT 0001C3 Packed Message Type: 2 from 10/161 to 10/1
    Attribute: 0191
    Date/Time: 19 Apr 16 18:57:54
    To : TAL System
    From : TAL System
    Subj : ^E:\SBBS\DOORS\INTERBBS\010\TAL\OUTBOUND\010T0601.172
    00000289


    Same thing happened to me over here with RObert. I never had PKT passwords set with him, just Session level. For some reason either the update added a PKT level password during the upgrade or he added one which was the same as Session level. When I upgraded here, it never took the session level and added it as a PKT level. I did exactly what you did and saw he was sending me PKT with a PKT pw so I added it in my INI file and haven't had an issue since. This was confirmed by Robert on my original PKT's being sent to him as they were marked BAD as well as I wasn't sending a PKT password either. When I added it on my end he didn't have an issue with the PKT's I sent.

    Janis' system was sending PKTs with no pw therefore Robert's system was tossing them as bad. I'll bet if Robert removes the PKT password from his INI then Janis' PKTs will toss perfectly.


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Lord Time on Wed Apr 20 10:05:00 2016
    Hiya Robert...

    Lord Time wrote to Digital Man <=-


    hmmm, I know I see the pw on the tic files, I'll have to let her know
    what going on, being she running linux (not sure what one) and the bbs software is bbbs, being it a all in one


    The PW in the TICs is your FILEFIX password and has nothing to do with PKT level passwords.


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Accession on Wed Apr 20 18:05:00 2016
    Accession wrote to Bill McGarrity <=-

    Hiya Nick...

    On 20 Apr 16 10:05, Bill McGarrity wrote to Lord Time:

    hmmm, I know I see the pw on the tic files, I'll have to let her
    know what going on, being she running linux (not sure what one)
    and the bbs software is bbbs, being it a all in one

    The PW in the TICs is your FILEFIX password and has nothing to do with
    PKT level passwords.

    Actually, I think with Deuce's TIC program as well as binkIT the TIC password is one in the same with the PKT password. I tried requesting
    that they should be different as it would cause problems (like it seems
    to be), but his thoughts were different on the matter.

    I'm not sure if Robert is running them or not. The programs deuce is working on should have their own pw's and be separate from PKT passwords. Either way I've setup Robert's info on my end using PKT pw's so all is well here.


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Deuce on Fri Apr 22 09:35:00 2016
    Deuce wrote to Bill McGarrity <=-

    Re: Re: Bugs Report (4/13/16)
    By: Bill McGarrity to Accession on Wed Apr 20 2016 06:05 pm

    I'm not sure if Robert is running them or not. The programs deuce is working on should have their own pw's and be separate from PKT passwords. Either way I've setup Robert's info on my end using PKT pw's so all is well here.

    TIC and packet passwords provide the same level of security in the same way over the same channels. The utilities I'm working on are intentionally simple and one of the ways I'm simplifying is to not
    require eight different (or more commonly identical) passwords to be configured for a single full-featured link.

    While other software doesn't do that, it's as easy to configure other software to use the same password as it it to use different passwords.

    I commend you on making SBBS as easy to work with as possible but in the reality of things and due to the fact you recognize "other" software doesn't do that, it does create issues down the line. If indeed you intend to remain fixed in your resolve then it should be important to advise those who use hatchit or binkit they need to send an areafix message to uplinks inserting a pkt password and advise downlinks to do the same. I speak from experience on this as Lord Time started using HatchIt and never told me or anyone else he was now using it therefore, at least in my instance, my secure folder had tons of BAD pkts. Yes, I was able to figure out the pw issue but I can see this being an ongoing thing in the future for new sysops.

    Just my thoughts on someone who's set in their ways of dealing with dedicated programs doing things you are now investing your time into making SBBS a better product. :)

    Thanks for your efforts...


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Lord Time on Fri Apr 22 17:15:00 2016
    Lord Time wrote to Bill McGarrity <=-

    While other software doesn't do that, it's as easy to configure other software to use the same password as it it to use different passwords.

    I commend you on making SBBS as easy to work with as possible but in the reality of things and due to the fact you recognize "other" software doesn't do that, it does create issues down the line. If indeed you intend to remain fixed in your resolve then it should be important to advise those who use hatchit or binkit they need to send an areafix message to uplinks inserting a pkt password and advise downlinks to do the same. I speak from experience on this as Lord Time started using HatchIt and never told me or anyone else he was now using it therefore,

    hmmm, I haven't use or setup hatchit or binkit here (maybe on my test
    bbs, but not on my main bbs), sbbsecho that is a different story


    Then I'm at a total loss as to why there was a pkt level password added on your end Doesn't really matter now being the issue has been resolved. :)



    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Lord Time on Fri Apr 22 21:16:00 2016
    Lord Time wrote to Bill McGarrity <=-

    While other software doesn't do that, it's as easy to configure other software to use the same password as it it to use different passwords.

    I commend you on making SBBS as easy to work with as possible but in the reality of things and due to the fact you recognize "other" software doesn't do that, it does create issues down the line. If indeed you intend to remain fixed in your resolve then it should be important to advise those who use hatchit or binkit they need to send an areafix message to uplinks inserting a pkt password and advise downlinks to do the same. I speak from experience on this as Lord Time started using HatchIt and never told me or anyone else he was now using it therefore,

    hmmm, I haven't use or setup hatchit or binkit here (maybe on my test bbs, but not on my main bbs), sbbsecho that is a different story

    Then I'm at a total loss as to why there was a pkt level password added on your end Doesn't really matter now being the issue has been resolved. :)

    thats was put in sbbsecho, a year ago (when you joined whispernet I put
    it in at that point and then when joined sport-net I put in there also)


    Impossible. We only started having this issue during the conversion to v3 of sbbsecho. I never had PKT passwords for either net to you.

    As I said, doesn't matter... it's water under the bridge. :)


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Deuce on Sat Apr 23 20:40:00 2016
    Deuce wrote to Bill McGarrity <=-

    Re: Re: Bugs Report (4/13/16)
    By: Bill McGarrity to Deuce on Fri Apr 22 2016 09:35 am

    I commend you on making SBBS as easy to work with as possible but in the reality of things and due to the fact you recognize "other" software doesn't do that, it does create issues down the line. If indeed you intend to remain fixed in your resolve then it should be important to advise those who use hatchit or binkit they need to send an areafix message to uplinks inserting a pkt password and advise downlinks to do the same. I speak from experience on this as Lord Time started using HatchIt and never told me or anyone else he was now using it therefore, at least in my instance, my secure folder had tons of BAD pkts. Yes, I was able to figure out the pw issue but I can see this being an ongoing thing in the future for new sysops.

    None of my utilities create or even currently use packets. TickIT (the TIC processor) does not have a configuration option for a TIC password,
    it uses the packet password from sbbsecho.ini. If the issue was bad packets, it had nothing to do with TickIT or HatchIT.

    OK, that shines a little more light onto the issue but, most if not ALL file processors require a password for FILEFIX. Being you need the PKT level password in echocfg to fulfill this requirement, it also puts added weight on those who don't want to use PKT passwords for echomail. As I said, in the future you may want to think about adding a toggle for TickIT in echocfg to allow a separate password free of the PKT password. Best of all worlds so to speak.



    Just my thoughts on someone who's set in their ways of dealing with dedicated programs doing things you are now investing your time into making SBBS a better product. :)

    These are a new set of dedicated programs, not "part of" Synchronet per se. FREQIT for example is for use with binkd and other SIF-supporting mailers (BinkIT doesn't support SIF, it does FREQ stuff internally
    using the same config info as FREQIT.js).

    OK... understood. I use ALLFIX for that.


    Right now, these new scripts are really only reccomended for people who are willing to keep an eye on their Fido traffic and are able to deal
    with problems when they inevitably crop up.

    Good deal. I am just trying to give another outlook on your work and please do not take it I am critizing it. Just a different viewpoint. :)


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Deuce on Mon Apr 25 14:59:00 2016
    Deuce wrote to Bill McGarrity <=-

    Re: Re: Bugs Report (4/13/16)
    By: Bill McGarrity to Deuce on Sat Apr 23 2016 08:40 pm

    OK, that shines a little more light onto the issue but, most if not ALL file processors require a password for FILEFIX. Being you need the PKT level password in echocfg to fulfill this requirement, it also puts added weight on those who don't want to use PKT passwords for echomail. As I said, in the future you may want to think about adding a toggle for TickIT in echocfg to allow a separate password free of the PKT password. Best of all worlds so to speak.

    If you don't want to use a packet password, you shouldn't want to use a TIC password either since they have the same role. I also haven't
    heard of a valid reason to have adifferent TICK vs packet password for
    the same link aside from the fact that it's possible.

    The thing is each has separate job to do, as I am sure you know. Areafix (echo) and filefix (tic) require passwords to control your available options from your uplink. PKT passwords are not part of that process at all. Echomail will operate fine without a PKT password. It's just protection from stray PKTs and, from what I've understood, have nothing to do with the actual mechanics of both operations.


    But yes, it will need to be documented that you need to configure the
    same password for TICK as for packets.

    Now, the *FIX passwords perform a different role than the packet/tick passwords and will be a separate configuration item... but I likely
    won't be supporting different FILEFIX vs AREAFIX passwords if I can
    avoid it (though that may be tricky).

    I think you're mistaken on the Filefix end of the password options as stated above.

    Best of all worlds so to speak.

    Having more things that need to be set correctly is "worse" in the definitions I'm using for this work, so adding more configuration
    options is not the best of all worlds, it's the worst possible outcome.

    Yes, I agree the KISS method is best but if that method breaks something that wasn't broken, especially when a PKT password was never needed unlike the *FIX passwords, then you may have issues.

    Good deal. I am just trying to give another outlook on your work and please do not take it I am critizing it. Just a different viewpoint. :)

    And I genuinely appreciate all feedback and suggestions, even when I reject them for now.

    Great... as long as we're both on the same page here. SBBS is a wonderful package and I love seeing it actively improved.

    Be well... :)


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)