1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • tickitjs does not match TicFilePwd when 4D address is used in .tic fil

    From Keyop Troy@1:103/705 to GitLab issue in main/sbbs on Fri Mar 19 13:44:09 2021
    open https://gitlab.synchro.net/main/sbbs/-/issues/240

    Within the fido config utility (echocfg) when entering a 4D address (NNN:NNN/NNN.0) the address is written in 3D format, i.e. with the point (0) removed. This works fine for most uses cases, however if an inbound .tic file uses a 4D address, then tickit.js will not match the Pw entry and TicFilePwd entry, and the following error occurs:Configured TicFilePwd is empty, but TIC file has a password, node: 39:13/0.0Suggested fix, within tickit.js as well as trying to match NNN:NNN/NNN also try NNN:NNN/NNN.0 in case 4D format is used in a .tic file.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 13:52:43 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1724

    Sounds like something isn't use the address parsing thing in the FIDO object. --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 13:56:14 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1725

    It would be helpful to have log lines before and after the error, not just the error. It looks like there's a weird hack to check passwords twice in some cases.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 13:58:45 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1726

    I've imported the file for now, by editing the sbbsecho.ini file and adding the .0 point, however any further edits with echocfg restore the address back to a 3D address.Also if 4D was added to echocfg, then I would imagine I would need to add every linked address twice, firstly in 3D format them 4D format, to cater for both types in .tic files.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:00:21 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1727

    The next time I get a file with a 4D address, I'll copy the whole text into this log.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:00:47 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1728

    The next time I get a file with a 4D address, I'll copy the whole text into this log.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From waldo kitty@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:04:49 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1729

    as the guy that added a lot to tickit and spent time in this particular area, i can say that tickit specifically does two rounds through the addresses in sbbsecho.ini looking for a remote system's password... the first loop is without the 5D domain and the second loop adds the 5D domain... it should be finding them in 4D or 5D mode...i really wanted to fix up the C/C++ code so that an address lookup would automatically work with either 4D or 5D FTN addresses but my C/C++ is woefully ugh...
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From waldo kitty@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:06:43 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1730

    .0?? that's interesting... x:y/z, x:y/z.0, x:y/z@foobar, and x:y/z.0@foobar should all be the same...
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:12:37 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1731

    That's right - it did two passes - one without the @ and one with.I will post the full text the next time it errors.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:16:54 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1732

    Agreed although tickit.js only checks for two of those four combinations at the moment I believe....
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From waldo kitty@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:19:47 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1733

    i'm just trying to understand how it missed the address... you only added the .0 in sbbsecho.ini?FWIW: FTN addressing is weird...fidonet started with only the node number aka 1D...then it added nets y/z for 2D...then points and zones both came about the same time... address representation may or may not be done with the zone so x:y/z and y/z.d are both 3D... when the zone is left off, your default zone is assumed...x:y/s.d is probably best known as 4D...finally @domain was added and then you have x:y/z@domain (5D) and y/z.d@domain (4D)...so you can see that there are two 3D and 4D representations in FTN software but few support the @domain format... my original work on tickit was was party to further true 5D in sbbs as well as enhancing tickit to work properly in a HUB configuration...
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From waldo kitty@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:21:17 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1734

    yeah, the C/C++ code should already be handling the .0 internally... i haven't been in the code in a couple of years, though... haven't even switched to git from cvs yet :(
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:23:11 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1735

    I'm assuming that tickit.js sees something like NNN:NNN/NNN.0 in the tic file, then searches sbbsecho.ini for a matching address, which it won't find, as the address is in 3D format - NNN:NNN/NNN
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From waldo kitty@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:25:09 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1736

    ahhhhh!!! in the TIC file? yeah, ok... can you grab that TIC the next time, too? i would really like to see it... mask out the password, of course...
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:25:52 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1737

    No problem.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From waldo kitty@1:103/705 to GitLab note in main/sbbs on Fri Mar 19 14:29:11 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1738

    yeah, that "weird hack" is to make it work with domains because i couldn't figure out the C/C++ code right to handle 3D/4D and 3D/4D+domain properly... initial attempts worked but were shot down for a reason i don't recall so i punted and just did the dual lookup in tickit... the attempts might have been due to adding more logging but it has been too long to remember that part clearly...
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Sat Mar 20 15:50:50 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1742

    This should be fixed with the most recent commit to fido_syscfg.js. Can you confirm?
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Sat Mar 20 17:02:25 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1743

    Hi Rob - what was the fix? (just so I know what I'm testing).
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Sat Mar 20 18:54:33 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1744

    A tic file address with a .0 point specified should match the same address (without the .0 point) from sbbsecho.ini now.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Sun Mar 21 12:38:06 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1746

    As soon as I get my next 4D .tic file I will you know. Might be Friday though for the next nodelist.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Fri Mar 26 15:51:12 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/240#note_1772

    So I've received the next nodelist from my hub and it went through ok, and I haven't tried the fix DigitalMan provided as I wanted to see it fail first before applying the latest code. Also my hub upgraded their system last weekend so this might explain why I don't have 4D problems this week. I will post another note on here if I spot the same problem again in future.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Tue Apr 13 01:00:38 2021
    close https://gitlab.synchro.net/main/sbbs/-/issues/240
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)