-=> Deuce wrote to Bill McGarrity <=-   
      
    De>   Re: Re: Bugs Report (4/13/16)   
    De>   By: Bill McGarrity to Deuce on Mon Apr 25 2016 02:59 pm   
      
    >  De> If you don't want to use a packet password, you shouldn't want to use a   
    >  De> TIC password either since they have the same role.  I also haven't   
    >  De> heard of a valid reason to have adifferent TICK vs packet password for   
    >  De> 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.   
      
    De> When I talk about a TICK password, I mean the one in the *.TIC file   
    De> which performs the same role as the packet password, not the filefix   
    De> password.   
      
   I get my files from Janis and we have a master password for filefix.  None of   
   the tics I receive from her have a password in the body of the tic file.  Now,   
   I use htick on my end and when I hatch a file it includes a pw but that can be   
   refined as such...   
      
   password: link's default password (generic - covers all below)   
   pktpwd: pktpassword for this link (echomail)   
   ticpwd: ticker password for this link (fileecho)   
   areafixpwd: areafix password for this link (echomail)   
   filefixpwd: filefix password for this link (FIleecho)   
      
   Being I just use it for files, the pkt and areafix passwords aren't used.  I   
   could just as easily defeat putting the pw into the actual tic file by   
   replacing "password" with "filefixpwd".     
      
      
    De> Similarly, when I talk about a packet password, I'm referring to the   
    De> one in the packet, not the one used for areafix messages.  The TICK   
    De> password and the PKT password provide the same role, just as the   
    De> areafix and filefix passwords do. But the TICK/PKT and *fix passwords   
    De> serve very different roles and absolutely *should* be different.   
      
    De> It sounds like you're conflating the TICK password with the Filefix   
    De> password.   
      
   Actually as I stated above, I'm not.  You're forcing echomail to use a PKT   
   password with the use of TickIT.  All I'm saying it should be an option    
      
      
    > 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.   
      
    De> TICK passwords are never needed either.   
      
   Agreed, so you're saying IF the PKT password was left blank then TickIT   
   wouldn't require one as well? Then that is fine but as Nick was saying, if   
   you're planning on moving further with the project to make TickIT a full   
   featured file processor then you'll have to seperate the TIC/PKT passwords from   
   the AreaFix/FileFix ones.   
      
   Either way, we seem to be on the same page so no sense in beating a dead horse   
   so to speak.  Was good chatting with you...   
      
   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)