• Re: Packet PW

    From Bill McGarrity@1:266/404 to Digital Man on Mon Nov 6 20:25:55 2017
    Digital Man wrote to Bill McGarrity <=-

    Re: Re: Packet PW
    By: Bill McGarrity to Digital Man on Wed May 04 2016 12:51 am

    Digital Man wrote to Joe Delahaye <=-

    Re: Re: Packet PW
    By: Joe Delahaye to Bill McGarrity on Tue May 03 2016 05:52 pm

    I also noticed a "Comment" was added in the form of the AREAFIX password we used.


    Saw that, but not sure what that is about.

    Can you elaborate? I don't know what is meant by this... a comment in the sbbsecho.ini file?

    In echocfg when you bring up linked nodes, to the right of node # there was my areafix password to that node. When I viewed that particular node information, the areafix pw was there along with a new section called Comment which had the same pw in it. I removed the Comment entry and esc out and the "comment" was no longer seen on the Linked Nodes column. It only happened to Robert Starr's node.

    That sounds like a bug. Can you re-run sbbsecho_upgrade.js (the latest revision) on your original sbbsecho.cfg, just as a test, and look at
    the resulting sbbecho.ini file and see if that anomoly exists? Or maybe
    it pops up after the first time you run echocfg with a newly upgraded sbbsecho.ini?

    If I can reproduce it (either the erroneous "comment" or a packet
    password that was not previously configured), then I can fix it. So
    far, I've been unable to reproduce these sightings.

    FYI, didn't happen this time....


    Ok, latest version of jsexec.exe, sbbsech_upgrade.js (v1.11)

    JSexec v3.17a-Win32 (rev 1.183) - Execute Synchronet JavaScript Module
    Compiled May 1 2016 05:04:28 with MSC 1800

    Loading configuration files from C:\SBBS\CTRL
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Reading script from c:\sbbs\exec\sbbsecho_upgrade.js c:\sbbs\exec\sbbsecho_upgrade.js compiled in 0.00 seconds C:\SBBS\CTRL\sbbsecho.cfg successfully converted to C:\SBBS\CTRL\sbbsecho.ini C:\SBBS\CTRL\sbbsecho.cfg renamed to C:\SBBS\CTRL\sbbsecho.cfg.old c:\sbbs\exec\sbbsecho_upgrade.js executed in 0.02 seconds

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    +[¦][?]--------+¦
    ¦ Linked Nodes ¦¦
    ¦--------------¦¦
    ¦ ¦3:ALL ¦¦
    ¦ ¦2:ALL ¦¦
    ¦ ¦1:ALL ¦¦
    ¦ ¦24:ALL ¦¦
    ¦ ¦1:3634/12 ¦¦
    ¦ ¦24:24/0 ¦¦
    ¦ ¦46:1/100 ¦¦
    ¦ ¦316:973/1 ¦¦
    ¦ ¦618:618/1 ¦¦
    ¦ ¦24:120/5 ¦¦
    ¦ ¦24:100/3 ¦¦
    ¦ ¦24:240/2 ¦¦
    ¦ ¦24:240/1 ¦¦
    ¦ ¦24:240/0 ¦¦
    ¦ ¦2:203/2 ¦¦
    ¦ ¦24:160/1 ¦¦
    ¦ ¦24:160/0 ¦¦
    ¦ ¦24:120/4 ¦¦
    ¦ ¦24:50/1 ¦¦
    ¦ ¦24:50/0 ¦]
    ¦ ¦24:120/3 ¦
    ¦ ¦24:140/2 ¦-
    ¦ ¦24:140/1 ¦M
    ¦ ¦24:140/0 ¦L
    ¦ ¦24:120/2 ¦L
    ¦ ¦24:100/2 ¦A
    ¦ ¦24:40/1 ¦N
    ¦ ¦24:40/0 ¦E
    ¦ ¦24:30/2 ¦P
    ¦ ¦24:30/1 ¦A
    ¦ ¦24:30/0 ¦-
    ¦ ¦24:10/1 ¦¦
    ¦ ¦24:24/2 ¦¦
    ¦ ¦24:20/2 ¦¦
    ¦ ¦24:20/1 ¦¦
    ¦ ¦24:20/0 ¦¦
    ¦ ¦24:110/2 ¦¦
    ¦ ¦1:135/371 ¦¦
    ¦ ¦24:100/1 ¦¦
    ¦ ¦24:100/0 ¦¦
    ¦ ¦24:10/0 ¦¦
    ¦ ¦24:24/1 ¦¦
    ¦ ¦24:110/1 ¦¦
    ¦ ¦24:110/0 ¦¦
    ¦ ¦1:298/7 ¦¦
    ¦ ¦2:203/0 ¦¦
    ¦ ¦618:100/1 ¦¦
    ¦ ¦1:229/300 ¦¦
    ¦ ¦316:77/1 ¦¦
    ¦ ¦1:261/38 ¦¦
    ¦ ¦1:266/512 ¦¦
    ¦ ¦ ¦¦
    +--------------+¦


    Nothing appeared in the area next to Robert's node # (316:77/1)

    Is there a debug mode I can use in the jsexec?


    --

    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Digital Man on Mon Nov 6 20:25:55 2017
    Digital Man wrote to Bill McGarrity <=-

    Re: Re: Packet PW
    By: Bill McGarrity to Digital Man on Wed May 04 2016 08:06 pm

    That sounds like a bug. Can you re-run sbbsecho_upgrade.js (the latest revision) on your original sbbsecho.cfg, just as a test, and look at the resulting sbbecho.ini file and see if that anomoly exists? Or maybe it pops up after the first time you run echocfg with a newly upgraded sbbsecho.ini?

    FYI, didn't happen this time....

    Ugh. The mystery remains then.

    I know...

    Nothing appeared in the area next to Robert's node # (316:77/1)

    What about the packet vs. areafix passwords? There were claims that the packet passwords were being "set" (in sbbsecho.ini) that weren't previously (in sbbsecho.cfg)?

    Nope, everything remained the same.... :(

    Is there a debug mode I can use in the jsexec?

    Not one that would help with this test.

    If anything should happen again for some strange reason I'll make sure I save all the log info.... whatever there is of it.


    --

    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Joe Delahaye on Mon Nov 6 20:25:55 2017
    Joe Delahaye wrote to All <=-

    I have not seen it referred to, so I am wondering. Since shortly after the upgrade to sbbsecho.v3, I had one node not tossing mail all of a sudden. Looking at the log files, there was an entry for a pcket PW missing. Found "" expected Password. I never had a packet PW with
    this node. He does not have one configured for me either. Yesterday another contact the same. No Packet Pw configured ever, and yet it requires one now. It just occurred to me that both these links are running the same mailer software, one of them is the author of DB, but
    I have other links also running DB, and so far no problem with them

    To be precise, it is the session PW that is now required as the Packet
    PW as well for some reason.

    That was my issue with Robert Starr. We'd connect with session pw... but sbbsecho was saying the pkt's were bad due to a missing pkt password. I never had one for Robert although he swears we did. I wasn't going to argue over it so I just added the one he was sending over to my sbbsecho.ini.

    Here are my logs...

    2016-04-12 22:18:57 Importing (secure) 12192104.pkt (Type 2+) from 316:77/1 2016-04-12 22:18:57 Imported: 1 msgs 3whispern <- WHISPERNET_ADMIN 2016-04-12 22:18:57 Imported: 1 msgs total in 0.0 sec (3157.9/min 52.6/sec)

    Now the following day...

    2016-04-13 01:46:53 Packet c:\fd\secure\12224859.pkt from 316:77/1 - Incorrect password ('??????' instead of '')
    2016-04-13 01:46:53 Bad packet detected: c:\fd\secure\12224859.pkt


    That's a difference of 4 hours and I'll bet between those times is when Robert updated to v3.

    This went on till I noticed the bad pkts in my inbound. Once I added the PKT pw, I renamed all the BAD pkts and sbbsecho imported them. Took me a week to find it.. lol...

    2016-04-20 10:55:09 Importing c:\fd\secure\19090240.pkt (Type 2+, 1.6KB) from 316:77/1 to 316:973/2
    2016-04-20 10:55:09 Importing c:\fd\secure\19090721.pkt (Type 2+, 2.9KB) from 316:77/1 to 316:973/2
    2016-04-20 10:55:09 Importing c:\fd\secure\19093025.pkt (Type 2+, 2.1KB) from 316:77/1 to 316:973/2
    2016-04-20 10:55:09 Importing c:\fd\secure\19204934.pkt (Type 2+, 5.1KB) from 316:77/1 to 316:973/2
    2016-04-20 10:55:09 Importing c:\fd\secure\19213626.pkt (Type 2+, 0.8KB) from 316:77/1 to 316:973/2
    2016-04-20 10:55:09 Importing c:\fd\secure\19220815.pkt (Type 2+, 1.2KB) from 316:77/1 to 316:973/2

    I also noticed a "Comment" was added in the form of the AREAFIX password we used.

    Just some thoughts...


    --

    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Joe Delahaye on Mon Nov 6 20:25:55 2017
    Joe Delahaye wrote to Bill McGarrity <=-

    Both my links are running DB. Nick and Roger, so far. Just waiting to see if personal packets from Ward, who also runs DB, is going to end up the same way. At this time, I dont know if SBBSEcho is somehow adding
    the session pw as a packet pw, or if it is DB, but like you said, this started with v3.



    I also noticed a "Comment" was added in the form of the AREAFIX password we used.


    Saw that, but not sure what that is about.

    I'll not speculate on who or what is causing it. It's a very easy solution to fix the problem but I was just pointing out you weren't the only one.. :)


    --

    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Digital Man on Mon Nov 6 20:25:55 2017
    Digital Man wrote to Joe Delahaye <=-

    Re: Re: Packet PW
    By: Joe Delahaye to Bill McGarrity on Tue May 03 2016 05:52 pm

    I also noticed a "Comment" was added in the form of the AREAFIX password we used.


    Saw that, but not sure what that is about.

    Can you elaborate? I don't know what is meant by this... a comment in
    the sbbsecho.ini file?

    In echocfg when you bring up linked nodes, to the right of node # there was my areafix password to that node. When I viewed that particular node information, the areafix pw was there along with a new section called Comment which had the same pw in it. I removed the Comment entry and esc out and the "comment" was no longer seen on the Linked Nodes column. It only happened to Robert Starr's node.


    --

    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
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)