TID: Mystic BBS 1.12 A46   
   MSGID: 4:900/107 e8dbbd8b   
   REPLY: 1:129/215 0fe88ac8   
   TZUTC: -0300   
   On 05 Apr 2021, g00r00 said the following...   
    g0> In the first quote it sounds to me like Mystic is requiring a password   
    g0> for the PKT because you've configured require a password for the PKT.   
      
   Hi! Thanks for the additional information!   
      
   It is a problem I have come across in the past.   
      
   My Hub provided me with a password, and did not specify for what I should use   
   it besides the obvious areafix request. So I set it up on every place on the   
   mystic node configuration that allowed me: PKT, TIC, AREAFIX, etc.   
      
   But, of course, the hub sends me .PKT files that do not require a password.   
   Mystic attempts to use the password anyway, and correctly so, because it is   
   configured to use a PKT password.   
      
   What I was wondering, is, instead of "invalid PKT" it could show "Attempted   
   to use password, but .PKT does not require it, please unconfigure it" .   
      
   Or something like it...   
      
   Sorry if I am not being clear, I think I talked about this with Nick two   
   years or so ago, and at that time I thought it was a bug in mystic.   
      
   What I am saying is, help the sysop discover the problem about the   
   not-required-to-be-configured password for an unprotected PKT.   
      
   Cheers!!!   
      
   --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)   
    * Origin: DaRK Game BBS (4:900/107)   
   SEEN-BY: 1/123 4/0 80/1 88/0 90/0 1 105/81 120/340 123/131 129/305   
   SEEN-BY: 135/367 226/30 227/114 702 229/101 424 426 452 550 664 700   
   SEEN-BY: 229/981 1016 1017 240/5832 249/206 307 317 400 282/1038 292/854   
   SEEN-BY: 317/3 322/757 342/200 633/280 900/0 100 102 106 107 108 902/0   
   SEEN-BY: 902/6 10 19 26 27 100   
   PATH: 900/107 902/27 90/1 229/426